When karma-webpack was switched to generating files on disk, only commons.js and runtime.js were configured to be served. This serves the rest of the contents of the output directory.
This PR contains a:
[x] bugfix
[ ] new feature
[ ] code refactor
[ ] test update
[ ] typo fix
[ ] metadata update
Motivation / Use-Case
I am attempting to update from karma-webpack@4, but bundles/assets generated by loaders (like workerize-loader, the library I am updating) are being served as 404's. This happens because of the hard-coded list of output files.
When karma-webpack was switched to generating files on disk, only
commons.js
andruntime.js
were configured to be served. This serves the rest of the contents of the output directory.This PR contains a:
Motivation / Use-Case
I am attempting to update from
karma-webpack@4
, but bundles/assets generated by loaders (like workerize-loader, the library I am updating) are being served as 404's. This happens because of the hard-coded list of output files.