Follow the advice below for configuring because karma does not serve assets and currently karma 5.1.1 with webpack 4.44.2 or some plugin of it crashes with OPs error above.Never, and I mean never use asset paths starting with a slash like /assets this will break your code in some cases.In component based CSS use relative paths going one level up. In html use relative paths starting with assets/.But when the GitLab runners execute it, it fails. ![]() Also oddly enough, it works perfectly when I run it locally. ![]() We've never had this error before and it worked fine previously. Our CI/CD pipelines stopped working on the "ng test" job and fails with the following error message: : TypeError: Cannot read property 'range' of undefinedĪt handleRangeHeaders (/builds/./node_modules/webpack-dev-middleware/lib/util.js:131:21)Īt processRequest (/builds/./node_modules/webpack-dev-middleware/lib/middleware.js:98:19)Īt ready (/builds/./node_modules/webpack-dev-middleware/lib/util.js:53:12)Īt handleRequest (/builds/./node_modules/webpack-dev-middleware/lib/util.js:182:5)Īt /builds/./node_modules/webpack-dev-middleware/lib/middleware.js:64:7Īt middleware (/builds/./node_modules/webpack-dev-middleware/lib/middleware.js:63:12)Īdded periods to sub out some specific repo names
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |