Module not found: Error: Cannot resolve module 'webpack-hot-middleware/client'
See original GitHub issueLike https://github.com/kadirahq/react-storybook/issues/205, tried adding this to an existing project using the guide
$ npm run storybook
...
> start-storybook -p 9001
=> Loading custom webpack config.
React Storybook started on => http://localhost:9001/
webpack built 98767b17b73fd7d3ae0a in 5067ms
Hash: 98767b17b73fd7d3ae0a
Version: webpack 1.13.1
Time: 5067ms
Asset Size Chunks Chunk Names
preview.bundle.js 3.97 MB 0 [emitted] preview
manager.bundle.js 796 kB 1 [emitted] manager
chunk {0} preview.bundle.js (preview) 1.43 MB [rendered]
[0] multi preview 52 bytes {0} [built] [1 error]
[1] ./~/process/browser.js 2.82 kB {0} [built]
[2] ./~/react/~/fbjs/lib/invariant.js 1.49 kB {0} [built]
[3] ./~/react/~/fbjs/lib/warning.js 1.75 kB {0} [built]
[4] ./~/object-assign/index.js 1.99 kB {0} [built]
[5] ./~/react/lib/ReactDOMComponentTree.js 6.17 kB {0} [built]
[6] ./~/react/react.js 56 bytes {0} [built]
[7] ./~/react-router/lib/routerWarning.js 845 bytes {0} [built]
[8] ./~/react/~/fbjs/lib/ExecutionEnvironment.js 1.06 kB {0} [built]
[9] ./~/invariant/browser.js 1.52 kB {0} [built]
...
[419] ./~/string.prototype.padend/polyfill.js 209 bytes {0} [built]
[420] ./~/string.prototype.padend/shim.js 316 bytes {0} [built]
[421] ./~/string.prototype.padstart/implementation.js 975 bytes {0} [built]
[422] ./~/string.prototype.padstart/polyfill.js 213 bytes {0} [built]
[423] ./~/string.prototype.padstart/shim.js 324 bytes {0} [built]
[424] ./src/scripts/components/lib/Button.less 1.09 kB {0} [built]
[425] ./src/scripts/components/lib/Icon.less 1.09 kB {0} [built]
[426] ./~/symbol-observable/index.js 101 bytes {0} [built]
[427] ./~/symbol-observable/ponyfill.js 350 bytes {0} [built]
[428] ./~/uuid/rng-browser.js 682 bytes {0} [built]
[429] ./~/uuid/uuid.js 5.29 kB {0} [built]
chunk {1} manager.bundle.js (manager) 324 kB [rendered]
[0] multi manager 28 bytes {1} [built]
[190] ./~/@kadira/storybook/dist/manager.js 324 kB {1} [built]
ERROR in multi preview
Module not found: Error: Cannot resolve module 'webpack-hot-middleware/client' in /Users/e.scha/Projects/project
@ multi preview
Really lost about how to resolve this, since I’m using npm version 3+ and no other similar bug reports have had an issue on this version.
$ npm -v && node -v
3.8.5
v5.6.0
Tried this already too:
$ rm -rf node_modules/
$ npm i webpack-hot-middleware --save-dev
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:14 (7 by maintainers)
Top Results From Across the Web
Error: Cannot resolve module 'webpack-hot-middleware/client ...
It's a very strange issue. At the moment I don't have time to further investigate. I also checked the global npm packages and...
Read more >Error: Can't resolve 'webpack-hot-middleware/client?path ...
Whenever I start the server, I get this error: Module not found: Error: Can't resolve 'webpack-hot-middleware/client?path=/__webpack_hmr&timeout ...
Read more >Error: Cannot resolve module 'webpack-hot-middleware/client'?
Even though already installed 'webpack-hot-middleware' it still says Module not found: Error: Cannot resolve module ...
Read more >Developers - Module not found: Error: Cannot resolve module ...
Module not found : Error: Cannot resolve module 'webpack-hot-middleware/client'
Read more >webpack-hot-middleware - npm
Webpack hot reloading you can attach to your own server. Latest version: 2.25.3, last published: a month ago.
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
It’s a very strange issue. At the moment I don’t have time to further investigate. I also checked the global npm packages and couldn’t find anything wrong with those.
I will update when I find out more.
@arunoda I will continue investigating and will report what I find. (I can’t share the current repo this is happening on, unfortunately)