search

storybookjs / vs-code-plugin

Aesop: a VSCode Extension to stage Storybook stories inside your IDE.
131 stars 15 forks source link

Issue running current version of extension with Storybook #9

Open jonniebigodes opened 4 years ago

jonniebigodes commented 4 years ago

First of all i would like to thank you for the time and effort you've put into this.

Now onto the issue at hand. While working on some updates on the documentation and reading about the release in twitter, i decided to use the extension and some issues have popped up.

I followed the instructions to install it and use it and i'm experiencing some "snafus" (pardon the bad pun).

In vscode pressing "F1" and selecting the command aesop awaken while Storybook is not running i can see the notification that it found a Storybook project and it then changes to "Retrieving running Storybook process" and it doesn't do anything, the extension window will not pop up. It will stay like that forever as you can see in the image below (this was after waiting for 10 minutes of waiting) aesop_storybook_issue_1

Also one other thing, if i'm already running Storybook and press "F1" and select the command "aesop awaken" it will spawn the window and i can see my Storybook. But if for any chance i close the window and i restart Storybook and enable the extension once more i'm presented with the following: aesop_storybook_issue_2

To add a bit more context i'm running the extension in

Version: 1.41.1 (user setup)
Commit: 26076a4de974ead31f97692a0d32f90d735645c0
Date: 2019-12-18T14:58:56.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362

Feel free to provide feedback so that we can close this issue and continue to improve this extension as i think that it would be a awesome resource to the Storybook community and depending on maintainers, something to be featured in the documentation.

keithrcagney commented 4 years ago

Thanks for bringing this to our attention! We're actively working on the instancing issue, with the hopes of correcting that shortly.

As for the hangup, we suspect it has to do with either Aesop's ps-node or netstat dependencies. At that stage, you should see a handoff from one Node.js child process to the parent Aesop process, but it seems to hang up on Windows-based systems in use cases where Aesop attempts to run the Storybook server for you. We're aiming to move towards a dependency-free and all-systems optimization soon.