-
Notifications
You must be signed in to change notification settings - Fork 2
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
Not able to run Story, Some Syntax issue #474
Comments
It looks like there are a couple problems launching the internal on-demand server on Windows. As a workaround, you can manually launch the dev server and configure the extension to use that instead: {
"storyExplorer.server.external.url": "http://localhost:6006", // adjust as needed
"storyExplorer.server.internal.enabled": false
} |
Instead of scanning just the launched process for an opened port that may be running a Storybook server, also check for opened ports by any child processes. This allows support for wrapper scripts that indirectly launch a Storybook server, as well as Windows support (where invoking a `start-storybook.cmd` script effectively does the same thing). Fixes #474
Instead of scanning just the launched process for an opened port that may be running a Storybook server, also check for opened ports by any child processes. This allows support for wrapper scripts that indirectly launch a Storybook server, as well as Windows support (where invoking a `start-storybook.cmd` script effectively does the same thing). Fixes #474
Thanks for the report. I just released 0.6.1, which I believe will fix this issue without requiring any workarounds. Please let me know if that turns out not to be the case. Incidentally, if you notice excessive memory consumption when you launch the on-demand server, make sure that you don't open the task output for the dev server while it's building. It's hidden by default, but while testing this out I noticed that, for some reason, memory usage would skyrocket if I opened it. I opened an issue with VS Code since I'm pretty sure it's an upstream bug (it repros even without the extension). But something to note, in case you encounter the same behavior. |
My package.json
The text was updated successfully, but these errors were encountered: