-
-
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
Dev server breaks with Node 18.0.0 + node-ip 1.1.5 #18019
Comments
Found a workaround. The error only comes if Storybook attempts to figure out the current network address So passing |
Same issue with Storybook 6.4 & Node 18. |
Thank you so much! That solved it for me. |
I'm running Storybook in Docker. The With the information above, I got it to work with the unspecific IPv4 address 0.0.0.0, i.e. by passing |
any landing fixes soon for this? |
I'm facing the same issue. Specifying My environment
.storybook/main.jsmodule.exports = {
stories: ['../src/**/*.stories.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx)'],
addons: [
'@storybook/addon-links',
'@storybook/addon-essentials',
'@storybook/addon-interactions',
],
framework: '@storybook/react',
core: {
builder: '@storybook/builder-vite',
},
}; Runned command
Result
|
@arayaryoma Please see #16555 for this issue. |
Meanwhile, node-ip@1.1.6 and node-ip2.0.0 have been released already including the fix. Fixing this issue should be a version bump now. (Fingers crossed.) |
See: storybookjs/storybook#18019 Should we resolved in `ip` version 1.1.6 or 2.0.0, see: indutny/node-ip@4de50ae
See: storybookjs/storybook#18019 Should we resolved in `ip` version 1.1.6 or 2.0.0, see: indutny/node-ip@4de50ae
See: storybookjs/storybook#18019 Should we resolved in `ip` version 1.1.6 or 2.0.0, see: indutny/node-ip@4de50ae adeira-source-id: 323b79bd85f45b13c82badc12790fb1030aa84d4
any news on this? |
@bonesoul This is fixed in |
As a workaround, what helped me to make storybook work with node 18, is install these addons and webpack
main.js
|
Great Caesar's ghost!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.5.6-alpha.0 containing PR #18330 that references this issue. Upgrade today to the
Closing this issue. Please re-open if you think there's still more to do. |
Good golly!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.5.6 containing PR #18330 that references this issue. Upgrade today to the
|
can confirm that updating node-ip to ^1.1.8 does fix the issue so if you can't upgrade your storybook for some reason, then you can add: "dependencies": {
"ip": "^1.1.8",
},
"resolutions": {
"ip": "^1.1.8"
}, to your package.json and you're good to go until you can update storybook. |
Edit: actually my issue is tracked at #16555 I seem to have this issue with following dependencies:
I can't run "ip" is on 1.1.8 as expected I am on 6.5.12 and it seemed to have been fixed in 6.5.6 already. I am using Node 18.12.0. The error message is specifically the one from @arayaryoma above, related to "crypto": #18019 (comment) |
export NODE_OPTIONS=--openssl-legacy-provider solved the issue for me |
Describe the bug
When updating to Node 18.0.0 start-storybook breaks with
To Reproduce
Launch a
start-storybook
with Node 18.0.0 and node-ip@1.1.5.System
System:
OS: Windows 10 10.0.19044
CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900KF
Binaries:
Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
npm: 8.6.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.19041.1266.0), Chromium (100.0.1185.44)
npmPackages:
@storybook/addon-a11y: ^6.4.22 => 6.4.22
@storybook/addon-docs: ^6.4.18 => 6.4.22
@storybook/addon-essentials: ^6.4.22 => 6.4.22
@storybook/addons: ^6.4.18 => 6.4.22
@storybook/builder-webpack5: ^6.4.18 => 6.4.22
@storybook/manager-webpack5: ^6.4.18 => 6.4.22
@storybook/theming: ^6.4.18 => 6.4.22
@storybook/vue3: ^6.4.18 => 6.4.22
Additional context
This is caused by the following Node 18 introduced
Undocumented change to "family" attribute in os.networkInterfaces() in Node 18.
Issue on node-ip along with a PR has been submitted.
The text was updated successfully, but these errors were encountered: