-
-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read property 'plugin' of null #105
Comments
me too! |
This should be fixed in master (8ba2ad7) - we just need to cut a release. |
it is also doesn't work in webpack2.2.0 |
@insin is there any idea about next release resolving this issue? |
Getting same error in webpack 2.2.1 |
well until they push a release. this works for me => npm install webpack-contrib/npm-install-webpack-plugin --save-dev |
|
hi there. Wondering when the latest fix will be published in npm platform. |
@ericclemmons could you publish a release pretty please? ;) |
me too |
same |
same here, new release is highly needed |
I have the same problem |
@david-whitlark : Thanks for your solution. |
@eblonvia I realized that the fix had been committed to the repo, but had not been pushed to npm, so by telling npm to install directly from the repo instead of npm allowed me to use the updated code |
I've published npm-install-webpack2-plugin to npm in the meantime (which is built from b21bd32) as I need a non-scoped (don't ask) Webpack 2 compatible version. These are the draft release notes I had ready for the next release:
|
Staled and fixed in master |
npm-install-webpack-plugin stop systematically with this error
I am using the example provided in this repository: https://github.com/webpack-contrib/npm-install-webpack-plugin/tree/master/example/webpack2
When running
npm run start
, dependencies seems to be resolve but not not the loadersnode 6.9.5 (LTS)
linux:
The text was updated successfully, but these errors were encountered: