Open Spider149 opened 1 year ago
I am currently experiencing this issue.
In addition to adding path aliases to the tsconfig, they must also be mirrored in the Webpack config. As far as I know, the only option at present is to eject.
It would be nice to have #58 to allow webpack config injections
I'm developing with js. Added jsconfig.json but the path like "@components/somecomponent" can not be resolved. My jsconfig.json
Vscode intelligence still suggest the @components but when I'm running npm run start, this path can't be resolved.