-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.1: Module resolution with baseUrl #13184
Comments
A quick fix is to use const { TsconfigPathsPlugin } = require('tsconfig-paths-webpack-plugin')
module.exports = {
webpackFinal: async (config) => {
config.resolve.plugins = [new TsconfigPathsPlugin({ extensions: config.resolve.extensions })]
return config
},
...
}; |
@Quadriphobs1 what version are you upgrading from? |
@shilman ^6.0.28 |
How were you able to get it working in 6.0.28? |
It works with 6.0.28... I am not sure why... But it does work... |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks! |
Thanks for the solution, adding TsconfigPathsPlugin worked for me (version 6.1.15) |
I had to use |
@balibebas any interest in submitting a PR with the update? |
Can do. But I'd like to answer this question before laying down a suggestion in the docs. #14087 (comment) |
@balibebas sorry, I didn't see a question ... what am I missing? 😄 |
Seeing as how I linked to your own comment I can see how that could be confusing. I've updated the link above to link to the related issue with the question. Whoops! :D |
Describe the bug
Upgrading to 6.1 failed to compile
Module not found: Error: Can't resolve 'components/**/**'
when using baseUrl with typescript, also fails using alias with typescript. It obviouslyScreenshots
If applicable, add screenshots to help explain your problem.
Additional context
I think storybook should use the project supplied tsconfig/jsconfig and maybe merge alongside any overrides, if its possible to probably do merging at this step
info => Removing existing JavaScript and TypeScript rules.
instead of removing, this would potentially make it more flexible to any environmentThe text was updated successfully, but these errors were encountered: