[Bug]: Angular Error with project initialization

[jonniebigodes]

Describe the bug

When a new user installs Storybook on an Angular application, it will throw an error and prevent it from automatically running with a cryptic error, leaving the user needing guidance on moving forward and getting Storybook running. This is probably related to the changes introduced in a previous release, which initialized Storybook after finishing the setup process. Upon testing this, it seems that Angular is the only one suffering from this.

For reference, here are two screenshots of the issue presenting itself in both the latest stable version and the beta:

@valentinpalkovic if you're aware of this and this is already reported and tracked anywhere, feel free to close this.

To Reproduce

• Initialize an Angular application
• Initialize Storybook using the latest stable version or the beta version
• Wait for the process to finish and verify the results.

System

No response

Additional context

No response

[mmorris8]

I'm hitting this as well.

Apparently you can run storybook afterwards and it will work. The command given in the output just before the error will work and may need to be manually copied into package.json.

[vanessayuenn]

@valentinpalkovic I think we can just handle the error if we are sure storybook actually can be run after that?