-
-
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
Upgrading to 6.1.14 opens http://192.168.1.48:6006/ instead of http://localhost:6006/ #13619
Comments
I can confirm it, I just upgraded to 6.1.14 and local address is not working. It drops a 404 error for vendors.bundle.js It only works if access it through network using my ip. |
Seem like this PR introduce this change: #13521 and this was released in 6.1.14. Now, storybook will always open with a specific address or IP address, instead of an option to open in localhost. |
Thank you @henrycity for the reference. @wanderlima You can use |
Personally I don't really need to see the IP address, all my projects are running on localhost using a different port, that's what I'm used to. But it's a matter of personal preference, so it's great the old url can still be used through configuration of the |
For my use case, it would still be valuable to see the IP address so that I can test on mobile or another computer. On the other hand, opening |
I've created a PR to address this issue by providing flexibility based on the provided args: #13812 Advice welcome on how to make sure this is properly covered in tests. |
Closing as dupe to #13707 |
Yowza!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.1.17 containing PR #13812 that references this issue. Upgrade today to the
|
Great Caesar's ghost!! I just released https://github.com/storybookjs/storybook/releases/tag/v6.2.0-alpha.22 containing PR #13812 that references this issue. Upgrade today to the
|
Describe the bug
Upgrading to 6.1.14 opens http://192.168.1.48:6006/ instead of http://localhost:6006/
It's a change in behavior, nothing critical.
Wasn't happening in v6.1.11
The text was updated successfully, but these errors were encountered: