You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running Storybook for Angular. I have a tsconfig project that contains the solution-stylesetup. But running storybook throws a bunch of warnings on this:
6% setup before compile angular-compiler<i> [webpack-dev-middleware] wait until bundle finished
Warning: The inferred tsconfig file "/Users/**/Documents/git/storybook-playground/tsconfig.json" appears to be "solution-style" since it contains no root files but does contain project references.
This is probably not wanted, since ngcc is unable to infer settings like "paths" mappings from such a file.
Perhaps you should have explicitly specified one of the referenced projects using the --tsconfig option. For example:
ngcc ... --tsconfig "./tsconfig.app.json"
ngcc ... --tsconfig "./tsconfig.ide.json"
ngcc ... --tsconfig "./tsconfig.spec.json"
Find out more about solution-style tsconfig at https://devblogs.microsoft.com/typescript/announcing-typescript-3-9/#solution-style-tsconfig.
If you did intend to use this file, then you can hide this warning by providing it explicitly:
ngcc ... --tsconfig "tsconfig.json"
What I don't get is why Storybook would catch that tsconfig file, since I have configured the setup to use the tsconfig.json inside the .storybook folder. And this tsconfig is based on the tsconfig.app.json in the root.
The option tsconfig is not a valid one for either of the configurations: storybook or build-storybook.
I'll get back to you if I manage to find a way to do this.
Describe the bug
Running Storybook for Angular. I have a tsconfig project that contains the
solution-style
setup. But running storybook throws a bunch of warnings on this:What I don't get is why Storybook would catch that tsconfig file, since I have configured the setup to use the
tsconfig.json
inside the.storybook
folder. And this tsconfig is based on thetsconfig.app.json
in the root.Why do I still get this logging?
To Reproduce
System
Additional context
No response
The text was updated successfully, but these errors were encountered: