-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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 build v4.0.0-alpha.17: missing @babel dependency #4071
Comments
Released a fix. Please give it a try! https://github.com/storybooks/storybook/releases/tag/v4.0.0-alpha.18 |
I installed all storybook deps to alpha.18,and now get a different error running storybook.
I did the following:
I can see in this error that I am properly linked. I then tried installing [email protected] (babel 7) in storybook lerna and core and get:
This is a typescript project, so I don't want to have babel or babel loader in my project. I would expect these deps to be handled in storybook. Just to test it out I installed @babel/core and [email protected] in my typescript project and storybook builds and runs fine. Everything worked for me on storybook alpha 16. EDIT: after re-reading this comment I realized I might have incorrectly installed babel-loader in storybook the first time, I am trying again. Sorry about that, I am new to using lerna/workspaces so it has been a struggle working with all these deps across packages and symlinks. EDIT2: I tried older babel-loader in core and root, and for some reason I get |
Do you have a |
We need to support different versions of babel so having |
I have a
The thing is, I don't use I just looked over alpha.17, which is what caused the peerDep on babel-loader: #3746. Adding the additional Cheers 🥂 |
I went ahead and installed alpha.18. It also requires I install @babel/core as I mentioned in a previous message. It really is unfortunate I have to add 2 deps for storybook that I don't actually use in my project. I'm not sure if this truly is a bug or intended, I imagine this changes the barrier of entry to using storybook on existing projects. At this point though, it is a different issue. |
But your storybook does. And to know which version to use, we need it to be installed on your side. And yes, you also need to install either
How does it look? |
|
If you are reporting a bug or requesting support, start here:
Bug or support request summary
After upgrading all storybook deps to the latest alpha (v4.0.0-alpha.17),
start-storybook
fails with with an error about missing@babel/plugin-proposal-class-properties
in @storybook/core.Steps to reproduce
start-storybook -p 6006 -c .storybook
Please specify which version of Storybook and optionally any affected addons that you're running
Affected platforms
macos
Screenshots / Screencast / Code Snippets (Optional)
The text was updated successfully, but these errors were encountered: