Open JReinhold opened 1 month ago
In @storybook/nextjs we both directly depend on tsconfig-paths and the wrapper tsconfig-paths-webpack-plugin:
@storybook/nextjs
tsconfig-paths
tsconfig-paths-webpack-plugin
https://github.com/storybookjs/storybook/blob/b23e84ad3ac8523d8f2372157cd6e5ddab9312b1/code/frameworks/nextjs/src/imports/webpack.ts#L1-L28
This seems unnecessary. We should be able to just use the webpack plugin directly. If it fails to load when the project isn't a TS project, wrap it in a try/catch block.
In
@storybook/nextjswe both directly depend ontsconfig-pathsand the wrappertsconfig-paths-webpack-plugin:https://github.com/storybookjs/storybook/blob/b23e84ad3ac8523d8f2372157cd6e5ddab9312b1/code/frameworks/nextjs/src/imports/webpack.ts#L1-L28
This seems unnecessary. We should be able to just use the webpack plugin directly. If it fails to load when the project isn't a TS project, wrap it in a try/catch block.