-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
5.1.0-rc.0 does not start: Error parsing babel config file #6864
Comments
Yeah this was a bad change made for #6633. We'll fix before the release |
Thanks for reporting @kaiyoma! |
related: #6634 |
Shiver me timbers!! I just released https://github.com/storybooks/storybook/releases/tag/v5.1.0-rc.2 containing PR #6878 that references this issue. Upgrade today to try it out! Because it's a pre-release you can find it on the Closing this issue. Please re-open if you think there's still more to do. |
Thanks, the new release fixed the config parsing issue, though we still can't upgrade because a lot of other functionality is still broken. See #6813. |
Huzzah!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.2.0-alpha.29 containing PR #7104 that references this issue. Upgrade today to try it out! You can find this prerelease on the |
Great Caesar's ghost!! I just released https://github.com/storybookjs/storybook/releases/tag/v5.1.9 containing PR #7104 that references this issue. Upgrade today to try it out! |
Describe the bug
After upgrading from 5.1.0-alpha.39 to 5.1.0-rc.0, Storybook does not start. It appears to be parsing a JavaScript file with a JSON parser.
Code snippets
Here's the shell output:
Our
.babelrc
file is proper JSON and does not have a "c" character at the beginning of the file, but ourbabel.config.js
does. It appears that Storybook is either trying to parse the wrong Babel config file or is using the wrong parser.We've never had this problem with any previous release of Storybook. Something changed in the last week or two to cause this.
System:
The text was updated successfully, but these errors were encountered: