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
When I extend from another project I do not receive TS errors but when I attempt to bundle I receive cannot find ./src/* file.
If I update the child tsconfig baseUrl and set to . everything works correctly.
If I remove ${configDir} from include config, esbuild/webpack build doesn`t throw errors but TS does.
Based on #3782 I believe you applied $configDir for paths configuration only, I believe it applies to any path defined within tsconfig ( including exclude and include ).
The text was updated successfully, but these errors were encountered:
ICJR
changed the title
$configDir may not be working correctly$configDir may not be working correctly
Jun 24, 2024
I believe esbuild-loader is not working correctly with $configDir.
This may be a bug with esbuild-loader instead of with esbuild. Please provide a way to reproduce the issue here that uses esbuild (not esbuild-loader). Note that this is the esbuild repo and esbuild-loader is a separate project (which you can find here). This repo has nothing to do with Webpack.
Based on #3782 I believe you applied $configDir for paths configuration only, I believe it applies to any path defined within tsconfig ( including exclude and include ).
The exclude and include fields are not used by esbuild's bundler: https://esbuild.github.io/content-types/#tsconfig-json. So it would be meaningless for esbuild to apply $configDir to them as it wouldn't have any effect on anything that esbuild does.
I believe
esbuild-loader
is not working correctly with$configDir
.implementation
configuration option to bring the latest esbuild package to webpack.cannot find ./src/* file
.baseUrl
and set to.
everything works correctly.${configDir}
frominclude
config, esbuild/webpack build doesn`t throw errors but TS does.Based on #3782 I believe you applied
$configDir
forpaths
configuration only, I believe it applies to any path defined within tsconfig ( includingexclude
andinclude
).The text was updated successfully, but these errors were encountered: