[Bug] Windows: When awakening aesop after it had been, it tries to start a new storybook server

[jonyeezs]

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

[giacomo9999]

Thanks so much for bringing this to our attention. What you're describing is a known issue (which seems to be Windows-specific and our team is a bit Mac/Linux-centric, so...) I'll try and have a look sometime in the next few weeks.