fix: skip sandbox validation for external modules in bazel-sandbox plugin #246
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.


The bazel-sandbox plugin throws errors when esbuild resolves external paths (marked via the external attribute), even though these paths are intentionally excluded from bundling and don't need to exist in the Bazel sandbox.
This change adds a check for result.external (https://esbuild.github.io/api/#external) before path validation, allowing external modules to bypass sandbox checks while maintaining security for bundled modules.
Fixes #245
Changes are visible to end-users: yes
A bug is fixed where files that are marked as external by esbuild are subjected to the bazel sandbox plugin path rules and rejected.
Test plan