• Dorian Johnson's avatar
    build: use static CSS and JS filenames in dev (#534) · 82d843e9
    Dorian Johnson authored
    In production, it's helpful to use content addressing to guarantee cache busting
    when publishing changes.
    
    However, in development, because the server serves a static copy of the
    index.html, that means that changing the Javascript bundle or CSS requires an
    otherwise-unnecessary restart of the server.
    
    This change makes the CSS and JS assets use fixed filenames so that a server
    restart isn't needed.
    
    Downside of this approach is there's now a dev/prod disparity and the config is
    more spread out between files. The positive is we don't need to modify the
    semantics of the server at all.
    82d843e9
Name
Last commit
Last update
..
css Loading commit data...
fonts Loading commit data...
images Loading commit data...
js Loading commit data...
templates Loading commit data...
.eslintignore Loading commit data...
.nvmrc Loading commit data...
global.d.ts Loading commit data...
jest.config.js Loading commit data...
package-lock.json Loading commit data...
package.json Loading commit data...
test-setup.ts Loading commit data...
tsconfig.eslint.json Loading commit data...
tsconfig.json Loading commit data...
tsconfig.webpack.json Loading commit data...
tslint.json Loading commit data...
webpack.common.ts Loading commit data...
webpack.dev.ts Loading commit data...
webpack.prod.ts Loading commit data...