Storybook build breaks if Spright depends on Nimble

[jattasNI]

🧹 Tech Debt

While developing the chat components I hit build issues in Storybook caused by a dependency I introduced from spright-components to nimble-components. For the chat components I worked around it by eliminating the dependency but that's not a viable long term strategy.

The problem is caused by the different ways that the storybook package and the spright-components package import content from nimble-components. All the storybook imports are relative paths to source (to keep turbosnap working) but all the components imports are package imports @ni/nimble-components (to ensure correct package dependencies in the build output). This results in 2 copies of nimble-components classes being pulled in to the storybook build, which leads to type conflicts.

@rajsite thought we might be able to use tsconfig type mappings similar to what we do in SystemLinkShared. We would apply this to storybook's config to map package paths to the corresponding relative paths. We should try this out and see if we can get the build and turbosnap working together.

[rajsite]

Found an existing chromatic issue where folks are having issues with monorepos and a description of the approach I was thinking of at stand-up is more spelled out (relying on package imports/exports and conditions). We might need to switch over to package entry points to even try it but guessing will hit issues as well.

[rajsite]

The tsconfig-paths-webpack-plugin may be useful for expressing paths in the tsconfig and having Webpack build be aware of it. Based on discussion from the exisiting chromatic monorepo issue.