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
@gleba It looks to me like you should be able to use tsconfig-paths and tsconfig-paths-webpack-plugin alongside Sucrase. Sucrase just does the code transformation step, and those two projects modify the path resolution behavior without transforming the code. Sucrase looks at files isolation without reading the filesystem, and doesn't care about or modify the string used in import statements, so any module resolution details should just work as long as they don't rely on code transformation.
There's some other discussion about using Sucrase to rewrite import statements here: #161 (comment) . Is that the sort of thing you were referring to?
Closing since I think I want to call filesystem-based path resolution out of scope for Sucrase (similar to how it's out of scope for tsc). Feel free to comment or file a new issue if you have a strong need for it.
What about typescript module resolution?
Something like as https://www.npmjs.com/package/tsconfig-paths
?
The text was updated successfully, but these errors were encountered: