fix(esbuild): add --preserve-symlinks flag by default and npm module mappings #2477
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
It was possible for esbuild to break out of the sandbox and find the
.ts
file inputs, this could be seen if the.ts
file was generated, as it would live in bazel-out/This also fixes an issue where external npm modules may not have gotten resolved correctly when bundling
Issue Number: N/A
What is the new behavior?
Bumps the tested version of esbuild and adds the
--preserve-symlinks
flag by default.Does this PR introduce a breaking change?
This will require uses to bump the version of esbuild used in their projects