fix(bundling): resolve index files from ts paths when running esbuild without bundling #23098
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
During build process a file
tmp/<path>/main-with-require-overrides.js
is generated to handlepaths
resolutions fromtsconfig
whenesbuild
is not running inbundle
mode.Having following
tsconfig.json
as exampleWe can use
lib1
in code as follows and during runtime it will automatically be resolved todist/apps/app1/libs/lib1/src/index.js
:Hovewer, when trying to use paths with wildcards, e.g.:
It gets resolved to
dist/apps/app1/apps/app1/src/config.js
andisFile
condition fails as such module doesn't exist, thus path is not replaced and runtime error is produced.Expected Behavior
During resolution of following code:
_resolveFilename
should consider all possible combinations of module path -dist/apps/app1/apps/app1/src/config.js
anddist/apps/app1/apps/app1/src/config/index.js