-
-
Notifications
You must be signed in to change notification settings - Fork 387
Cannot destructure property createHash
of 'undefined' or 'null'.
#69
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
Comments
it's need to update wepback from ^4.1.0 to ^4.3.0 |
I had to downgrade from webpack 4.5 to 4.4 to get this to work with v0.4 of the plugin. |
I updated to Webpack ^4.8.3 and my build compiled again. |
I'm getting this error on webpack |
This is happenning to me with webpack 4.16 and mini-css-extract-plugin 0.4.1. Any solutions? |
- next 6.1.1-canary.5 - nwb 0.23.0 - react-tree-walker 4.3.0 - stats-webpack-plugin 0.7.0 - webpack-bundle-analyzer 3.0.2 [email protected] is required because nwb has been updated to webpack 4, causing these issues: - webpack-contrib/mini-css-extract-plugin#69 - insin/nwb#473 - https://github.com/zeit/next.js/releases/tag/6.1.1-canary.3 is the first version with webpack 4 and 6.1.2 still uses webpack 3...
* Use Node.js LTS (8.12.0) * Update standard 12.0.1 * Dependency version bumps: - isomorphic-unfetch 2.1.1 - lodash 4.17.11 - react 16.5.0 - react-dom 16.5.0 - sanitize-html 1.19.0 * Dependency version bumps: - next 6.1.1-canary.5 - nwb 0.23.0 - react-tree-walker 4.3.0 - stats-webpack-plugin 0.7.0 - webpack-bundle-analyzer 3.0.2 [email protected] is required because nwb has been updated to webpack 4, causing these issues: - webpack-contrib/mini-css-extract-plugin#69 - insin/nwb#473 - https://github.com/zeit/next.js/releases/tag/6.1.1-canary.3 is the first version with webpack 4 and 6.1.2 still uses webpack 3...
i upgraded Nextjs 6.1.1 to Nextjs 7.0.2. |
|
fixed by installing latest version of webpack. |
Using |
same error in [email protected] and @4.34.0 |
This is the only thing that worked for me:
|
when build with [email protected],the shell show that info:
The text was updated successfully, but these errors were encountered: