Replies: 3 comments 2 replies
-
Thanks for bring this up. So far we could tell is that rolldown provided the ability of aliasing, but for
we need to evaluate if this should be done by a bundler itself or an upper level tools. |
Beta Was this translation helpful? Give feedback.
-
FYI esbuild does it (but I don't how complete it is). I see, I guess an alternative would be Rolldown accepting a path alias parameter (albeit less correct since it'd be global and couldn't account for multiple |
Beta Was this translation helpful? Give feedback.
-
I believe the main benefit of using vite-tsconfig-paths or providing a |
Beta Was this translation helpful? Give feedback.
-
Extracting the path alias information defined by
tsconfig.json#compilerOptions.paths
andpackage.json#imports
isn't trivial. For example if the user has multipletsconfig.json
files.It could make sense if the path alias information, which Rolldown needs to extracts from
tsconfig.json
andpackage.json
anyways, is publicly exposed for tools built on top of Rolldown such as Vite.If Vite uses that information, then Vite users won't have to define path aliases redundantly in
vite.config.js
anymore. Making vite-tsconfig-paths obsolete.Beta Was this translation helpful? Give feedback.
All reactions