chore(deps): bump esbuild ^0.25.0 -> ^0.28.1 (fixes SNYK-JS-ESBUILD-17750822)#1502
Closed
juar-queue-it wants to merge 1 commit into
Closed
chore(deps): bump esbuild ^0.25.0 -> ^0.28.1 (fixes SNYK-JS-ESBUILD-17750822)#1502juar-queue-it wants to merge 1 commit into
juar-queue-it wants to merge 1 commit into
Conversation
juar-queue-it
force-pushed
the
test/esbuild-0.28-bump
branch
from
July 13, 2026 12:07
f3fc306 to
9dbe38e
Compare
Author
|
Hi everyone. I'm bumping up the dependency to |
Member
|
replaced by #1506 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Bumps the
esbuilddependency from^0.25.0to^0.28.1.The pinned
^0.25.0range keepsesbuildon0.25.x, which is flagged by Snyk as SNYK-JS-ESBUILD-17750822 — "Resources Downloaded over Insecure Protocol" (CWE-426, CVSS 9.2). The advisory covers>=0.17.0 <0.28.1and is fixed in0.28.1. Because the range is^0.25.0, downstream consumers cannot pull the fix without an override — Snyk reports "no remediation path available" until@fastly/js-computebumps it here.esbuildis only used in the JS bundler step of the CLI (src/compiler-steps/bundle.tsand the twosrc/esbuild-plugins/*), so this has no effect on the StarlingMonkey/Wasm runtime.Verification
With
esbuild@0.28.1installed:npx tsc(build:cli) — passesnpm run test:types(tsd) — passesbuild()through both Fastly plugins (fastlyPlugin+swallowTopLevelExportsPlugin) against a sample app:fastly:*imports resolve correctly and top-level exports are swallowed as expected.The esbuild API surface used here (
build({...})plus theonResolve/onLoadplugin hooks) is unchanged across0.25→0.28, so no source changes were required.🤖 Generated with Claude Code