webpack 2.1.0-beta.14 Uncaught Exception
See original GitHub issuewebpack 2.1.0-beta.14 will throw the following error.
CarteBlanche started at /carte-blanche
Uncaught Exception...
TypeError: d.getWarnings is not a function
at <project>/node_modules/webpack/lib/Compilation.js:594:21
at Array.forEach (native)
at <project>/node_modules/webpack/lib/Compilation.js:593:22
at Array.forEach (native)
at Compilation.reportDependencyWarnings (<project>/node_modules/webpack/lib/Compilation.js:592:9)
at Compilation.<anonymous> (<project>/node_modules/webpack/lib/Compilation.js:483:8)
at Array.forEach (native)
at Compilation.seal (<project>/node_modules/webpack/lib/Compilation.js:482:15)
at Compiler.<anonymous> (<project>/node_modules/webpack/lib/Compiler.js:431:15)
at <project>/node_modules/webpack/node_modules/tapable/lib/Tapable.js:152:11
at Compilation.<anonymous> (<project>/node_modules/webpack/lib/Compilation.js:430:10)
at <project>/node_modules/webpack/lib/Compilation.js:405:12
at <project>/node_modules/webpack/lib/Compilation.js:320:10
at <project>/node_modules/async/lib/async.js:52:16
at done (<project>/node_modules/async/lib/async.js:246:17)
at <project>/node_modules/async/lib/async.js:44:16
Uncaught Exception...
undefined
I didn’t have time to look into why this is happening, but I’ve narrowed it down to being in the .14 release.
Temporary Fix
downgrade to webpack 2.1.0-beta.13
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Webpack 5 issue with Angular 12 causing resource busy or ...
Working on a project that uses Angular 12 and Webpack 5, it seems that i am ... 0/0 modulesnode:internal/process/promises:279 triggerUncaughtException(err, ...
Read more >How to Prevent Webpack Error after npm Install?
It seems to work now with webpack 2.1.0-beta.22 , but you got another error. This error happened because extract-text-webpack-plugin is not of the...
Read more >an unhandled exception occurred: invalid configuration object ...
an unhandled exception occurred: invalid configuration object. webpack has been initialized using a configuration object that does not match the api schema.
Read more >Compare Versions | webpack-dev-server | npm
Serves a webpack app. Updates the browser on changes. Serves a webpack app. Updates the browser on changes. Licenses. Licenses.
Read more >Entry Points - webpack
We will show you the ways you can configure the entry property, in addition to explaining why it may be useful to you....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like the extra-entry-plugin should have a peerDependency to webpack instead of a depenency. And webpack@^2.1.0-beta need to be included.
https://github.com/jantimon/extra-entry-webpack-plugin/blob/master/package.json#L46
👍