I currently evaluating the migration of a very very lange and complex webpack configuration to esbuild.
I have found some esbuild plugins but was not able to get things working and believe that build-in support for aliases similar to resolve.alias in webpack or paths in TypeScript would be a very helpful addition.
The text was updated successfully, but these errors were encountered:
@evanw Interesting, but I'm not sure I fully understand. I would prefer to just rely use the build-in features but noticed, that esbuild did automatically resolve the TypeScript modules but not the css modules. Is this this the expected behavior or should also the css modules be resolved? Please also note, that I created a separate SR #2192 that specifically focuses on the module resolution when chaining plugins. Thank you for your awesome work.
I also noticed that for example the dataurl loader needed to import image resources does not resolve accordingto the paths in tsconfig.json and does also not observe the alias set in the plugin esbuild-plugin-alias.