storybook fails with unmodified repo, and with meteor 1.3.2.4

Question

storybook fails with unmodified repo, and with meteor 1.3.2.4

cellog opened this issue 8 years ago · comments

ERROR in multi preview
Module not found: Error: Cannot resolve module 'webpack-hot-middleware/client' in /Users/gbeaver2/github/local/mantra-sample-blog-app
@ multi preview

ERROR in multi preview
Module not found: Error: Cannot resolve module 'babel' in /Users/gbeaver2/github/local/mantra-sample-blog-app
@ multi preview

Gregory Beaver · Answer 1 · Tue May 03 2016 12:45:22 GMT+0800 (China Standard Time)

after meteor npm i webpackage-hot-middleware babel:

ERROR in The node API for babel has been moved to babel-core.
@ multi preview

Gregory Beaver · Answer 2 · Tue May 03 2016 23:14:38 GMT+0800 (China Standard Time)

update: when using bundled npm with meteor (meteor npm) it fails, because it is version 2. I updated meteor/node to latest, and re-installed everything manually (npm i --save blahblah and npm i --save-dev blahblah) and now we're cooking.

Sascha1337 · Answer 3 · Mon May 09 2016 21:58:54 GMT+0800 (China Standard Time)

thank you for the hint related to npm version, npm install -g npm, rm -rf node_modules, npm install did it for me, too. 👍

Josh · Answer 4 · Mon May 09 2016 22:07:54 GMT+0800 (China Standard Time)

I'm unsure about the Cannot resolve module 'webpack-hot-middleware/client' error, but the Module not found was resolved with Storybook v1.22.1 -> storybookjs/storybook#167

Sascha1337 · Answer 5 · Mon May 09 2016 22:09:47 GMT+0800 (China Standard Time)

I had this bug using Storybook v1.22.1 with fresh mantra-sample-blog-app from git, so it may not be fixed in all cases?

EDIT: My fault, i was using npm 2 and even in the README file there's a clue to use npm 3 i did not see.