-
Notifications
You must be signed in to change notification settings - Fork 422
throw new InitializationError() #590
Comments
This seems to be the issue:
You could either look at bundle.js:34992:71 and try to understand what's going on there. In a nutshell, the code is doing something that's not currently supported by Prepack along the global code. Could be a loop over some values that cannot be determined at build time, or could be something else. Prepack is not yet ready for use in production, and one of the remaining issues is having better error message... |
When the prepack plug-in is turned off, the build shows the following code(34992:71) :
After I decided to try to start the prepack of an already compiled but not minifined project:
P.S. I know what prepack is young but will be cool if it will can work with webpack |
Also see here: #544. |
This really fixes the bug with webpackJsonp is not defined, but this test was performed for the unpacked version. As for further work, I received such an answer:
|
another same InitializationError issue within Gulpjs |
edited reason: irrelevant, red herring. |
Do you have steps for us to reproduce the issue? |
Closing, as we couldn't make progress on the diagnosis. Feel free to re-open with new information. |
Hello! I added prepack-webpack-plugin plugin for my project how use your package. After I have error message with compilation.
Author of plugin are claims what this problem from you side.
Original issues: gajus/prepack-webpack-plugin#17
Details:
Packege.json :
webpack config:
log from npm
The text was updated successfully, but these errors were encountered: