Let's get move involved, and move this into the storybook org on github?

https://github.com/storybookjs

I think https://github.com/storybookjs/vs-code-plugin would be a great repo name? WDYT?

I have a project where the Storybook has been installed in a sub-directory of the project root.
I could see support for this in two ways - provide a setting to configure the path to the directory where Storybook is installed or provide support for VS Codes Workspaces. With support for Workspaces, I could include my sub-directory as a workspace folder, making it a kind of root directory for Aesop to scan for Storybook installations.

Describe the bug

When I have a running storybook server from the first aesop awaken.
Running that command again seem to spawn another command to start up storybook.

It then creates multiple tabs of aesop.

Steps to reproduce the behavior

1. Run awaken aesop
2. Wait till server starts and aesop pops up
3. Run awaken aesop again
4. Another terminal is created that's starting the server
5. Multiple aesop tabs pop up.

Expected behavior

If an existing server is running, it should just open the webview instead of running another command.

Screenshots and/or logs

Things to notice:

• On the first awaken aesop it didn't pop up the aesop view
• On the second attempt it tried to open it again and as well open 2 aesop tabs
• Every time awaken aesop is activated it just generates more tabs.

Environment

• OS: Windows
• Node.js version: v12.18.3
• NPM version: 6.4.1
• VSCode version (if applicable): 1.53.0-insider

Describe the bug

When I do aesop awaken, I get the following back immediately:

Failed looking for running Node processes. Error: your 131072x1 screen size is bogus. expect trouble

Environment

• OS: Windows 10 + Ubuntu 20 in WSL2
• Node.js version: v12.20.0
• NPM version: 6.4.18

Additional context

My guess would be that this is something to do with running VSCode in WSL.

Really excited about Aesop, so I hope this is fixable!

I'd love to be able to debug and test this locally, but right now I have not a clue on how to actually do this.

Could we add a contribution guide so other people could understand how to develop this locally?

Thank you so much for developing this addon! I see so much potential in it! Here's a bug that is getting on my way currently:

Describe the bug

When loading Aesop, I'd expect my Storybook to take the full height of the editor, but unfortunately that's not the case.

Steps to reproduce the behavior

1. Awaken aesop
2. See the gap at the bottom

Expected behavior

The preview takes full height so users can better visualize the addon panel without feeling cluttered.

Screenshots and/or logs

Environment

• OS: macOS Catalina

Extra remarks

I also have the feeling that the webview is scaled up. The fonts are bigger, it feels too tight.

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)

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:

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.