Skip to content

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

Closed
clojurie opened this issue Mar 29, 2018 · 11 comments
Closed

Cannot destructure property createHash of 'undefined' or 'null'. #69

clojurie opened this issue Mar 29, 2018 · 11 comments

Comments

@clojurie
Copy link

when build with [email protected],the shell show that info:

const { Template, util: { createHash } } = _webpack2.default;
                          ^
TypeError: Cannot destructure property `createHash` of 'undefined' or 'null'.
@clojurie
Copy link
Author

it's need to update wepback from ^4.1.0 to ^4.3.0

@sokra sokra closed this as completed Mar 29, 2018
@taylor1791
Copy link

taylor1791 commented Apr 26, 2018

I had to downgrade from webpack 4.5 to 4.4 to get this to work with v0.4 of the plugin.

@EddyVinck
Copy link

I updated to Webpack ^4.8.3 and my build compiled again.

@clayrisser
Copy link

I'm getting this error on webpack 4.16

@vpalos
Copy link

vpalos commented Aug 17, 2018

This is happenning to me with webpack 4.16 and mini-css-extract-plugin 0.4.1.

Any solutions?

daohoangson added a commit to daohoangson/js-tinhte-api that referenced this issue Sep 13, 2018
- 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...
daohoangson added a commit to daohoangson/js-tinhte-api that referenced this issue Sep 13, 2018
* 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...
@min9nim
Copy link

min9nim commented Oct 28, 2018

i upgraded Nextjs 6.1.1 to Nextjs 7.0.2.
and it works!

@kevnk
Copy link

kevnk commented Dec 7, 2018

npm i mini-css-extract-plugin -D fixed it for me

@kdevsoftware
Copy link

fixed by installing latest version of webpack.
npm i webpack --save

@aeksco
Copy link

aeksco commented Apr 16, 2019

Using next version 8.0.4 - adding webpack at 4.8.3 as a dev dependency solved the problem, but I couldn't for the life of me say what was broken or how the update fixed it. Blew at least 3 hours today battling my dependencies. Intensely frustrating - thanks a million @EddyVinck, you're a lifesaver!

@maxHoo
Copy link

maxHoo commented Jun 13, 2019

same error in [email protected] and @4.34.0

@anirudhajith
Copy link

This is the only thing that worked for me:

npm install -g npm@latest
rm -rf node_modules
npm install

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests