-
-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: envelope routines::unsupported #21739
Comments
Have you tried running it with NODE_OPTIONS="--openssl-legacy-provider" ? |
Please try upgrading to the latest prerelease. Migration guide: https://storybook.js.org/migration-guides/7.0 |
I tried
I tried this solution, it works with storybook ✅ |
It seems that generally there are two solutions:
As 2 seems a bit risky to have non-stable version in production so, seems option 1 the best for now. |
@shilman Hello there, I think this issue still persists even with storybook v7. I encountered this issue while I was following one of the tutorials Design Systems for Developers. I have a reproducible repo here: sookmax/learnstorybook-design-system. Repo dependencies information
Checking out the repo and run the following commands will produce the error at the end of the build process:
P.S. The suggested workaround using |
TL;DR Updating Webpack and Storybook to latest version fixed this for me. I had this happen with Storybook v6.3.8 and Node v18.16.1. I tried updating Webpack to latest version, but that didn't work. Previously I was on v5.54.0 and upgrading to latest v5.88.1 didn't help. I updated to Storybook v7.0.27 without the Webpack upgrade and that also failed. Updating both Storybook and Webpack to latest version resolved this issue for me. Storybook 6.3.8 + Webpack 5.54.0 -- Didn't work Storybook 7.0.27 + Webpack 5.54.0 -- Didn't work |
Another answer: https://stackoverflow.com/a/73027407/2391795 |
Describe the bug
node
projectreact
andstorybook
up-to-date versionsstart-storybook
scriptsTo Reproduce
storybook fails to run on Node v18.x
logs
The text was updated successfully, but these errors were encountered: