Bump esbuild, @fastly/compute-js-static-publish, @fastly/js-compute and @fastly/serve-vercel-build-output

[dependabot]

Bumps esbuild to 0.25.1 and updates ancestor dependencies esbuild, @fastly/compute-js-static-publish, @fastly/js-compute and @fastly/serve-vercel-build-output. These dependencies need to be updated together.

Updates esbuild from 0.17.19 to 0.25.1

Release notes

Sourced from esbuild's releases.

v0.25.1

• Fix incorrect paths in inline source maps (#4070, #4075, #4105)

  This fixes a regression from version 0.25.0 where esbuild didn't correctly resolve relative paths contained within source maps in inline sourceMappingURL data URLs. The paths were incorrectly being passed through as-is instead of being resolved relative to the source file containing the sourceMappingURL comment, which was due to the data URL not being a file URL. This regression has been fixed, and this case now has test coverage.

• Fix invalid generated source maps (#4080, #4082, #4104, #4107)

  This release fixes a regression from version 0.24.1 that could cause esbuild to generate invalid source maps. Specifically under certain conditions, esbuild could generate a mapping with an out-of-bounds source index. It was introduced by code that attempted to improve esbuild's handling of "null" entries in source maps (i.e. mappings with a generated position but no original position). This regression has been fixed.

  This fix was contributed by @​jridgewell.

• Fix a regression with non-file source map paths (#4078)

  The format of paths in source maps that aren't in the file namespace was unintentionally changed in version 0.25.0. Path namespaces is an esbuild-specific concept that is optionally available for plugins to use to distinguish paths from file paths and from paths meant for other plugins. Previously the namespace was prepended to the path joined with a : character, but version 0.25.0 unintentionally failed to prepend the namespace. The previous behavior has been restored.

• Fix a crash with switch optimization (#4088)

  The new code in the previous release to optimize dead code in switch statements accidentally introduced a crash in the edge case where one or more switch case values include a function expression. This is because esbuild now visits the case values first to determine whether any cases are dead code, and then visits the case bodies once the dead code status is known. That triggered some internal asserts that guard against traversing the AST in an unexpected order. This crash has been fixed by changing esbuild to expect the new traversal ordering. Here's an example of affected code:

  switch (x) {
    case '':
      return y.map(z => z.value)
    case y.map(z => z.key).join(','):
      return []
  }

• Update Go from 1.23.5 to 1.23.7 (#4076, #4077)

  This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses.

  This PR was contributed by @​MikeWillCook.

v0.25.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.24.0 or ~0.24.0. See npm's documentation about semver for more information.

• Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

  This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

  Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

  In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

  Thanks to @​sapphi-red for reporting this issue.

• Delete output files when a build fails in watch mode (#3643)

  It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

• Fix TypeScript-specific class transform edge case (#3559)

  The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

  // Original code
  class Foo extends Bar {
    #private = 1;
    public: any;
    constructor() {
      super();
    }
  }
  // Old output (with esbuild v0.19.9)
  class Foo extends Bar {
  constructor() {
  super();
  this.#private = 1;
  }
  #private;
  }
  // Old output (with esbuild v0.19.10)
  class Foo extends Bar {
  constructor() {
  this.#private = 1;
  super();
  }
  #private;
  }
  // New output
  class Foo extends Bar {
  #private = 1;
  constructor() {
  super();
  }
  }

• Minifier: allow reording a primitive past a side-effect (#3568)

  The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (truncated)

Commits

• 6bfc1c1 publish 0.25.1 to npm
• f9b3952 fix #4078: prepend namespaces to source map paths
• ccf3dd7 add "contributed by" in changelog
• 48cd7a9 Update Go from 1.23.5 to 1.23.7 (#4077)
• 1f04fa4 fix absolute windows paths in source maps
• 9ca03f6 also add test case from #4075
• 2f244c0 add test case from #4104
• 1dde994 fix incorrect test names
• 9f008c5 fix #4070: file namespace for sourceMappingURL
• cbd5eb8 release notes and tests for #4082
• Additional commits viewable in compare view

Updates @fastly/compute-js-static-publish from 5.0.0 to 5.2.1

Changelog

Sourced from @​fastly/compute-js-static-publish's changelog.

[5.2.1] - 2023-11-14

Updated

• Apply "Compute" branding change.

[5.2.0] - 2023-09-19

Changed

• Use @fastly/js-compute@3 for dev
• Make generated project use @fastly/js-compute@3

[5.1.2] - 2023-09-19

Added

• Added support for @fastly/js-compute 3.0.0

[5.1.1] - 2023-07-06

Fixed

• Fix: Specify full path in import directives in generated files to allow use in projects with "type": "module".

[5.1.0] - 2023-06-12

Fixed

• Fix: Correct package.json created by init-app to reference fastly/js-compute@2 (#8)

[5.0.2] - 2023-05-25

Updated

• README updates

[5.0.1] - 2023-05-19

Fixed

• Avoid a crash caused by extra output when fastly CLI tool detects a newer available version.

Commits

• 728d2a5 v5.2.1
• e2a0fcf Merge pull request #11 from fastly/kats/branding-change
• 6f2c8d2 Apply "Compute" branding change.
• 217e972 v5.2.0
• f206e51 Changelog
• 12b657a Fix version list in Changelog
• 9ccd86a Use @​fastly/js-compute@​3 for dev
• 61d94f5 Make built app use @​fastly/js-compute@​3
• 0c64ee3 v5.1.2
• 3f21cd5 Add @​fastly/js-compute ^3 as peer dependency
• Additional commits viewable in compare view

Updates @fastly/js-compute from 2.0.0 to 3.33.1

Release notes

Sourced from @​fastly/js-compute's releases.

v3.33.1

3.33.1 (2025-03-12)

Bug Fixes

• documentation fix (#1147) (15b9ea5)

v3.33.0

3.33.0 (2025-03-12)

Features

• add support for EventTarget (#1145) (a735993)
• FormData support and Request.formData and Response.formData (#1144) (0214ae7)

Bug Fixes

• Backend.prototype.health method definition (#1143) (42d429b)
• Weval stack overflow bug (#1135) (f6947d9)

v3.32.2

3.32.2 (2025-02-26)

Bug Fixes

• ready-based immediate task indexing (#1129) (8cfad4f)

v3.32.1

3.32.1 (2025-02-20)

Bug Fixes

• docs server toolchain fix (#1124) (c2490d1)

v3.32.0

3.32.0 (2025-02-20)

Features

• Acl Support (#1073) (0f93f7b)

v3.31.0

3.31.0 (2025-02-14)

... (truncated)

Changelog

Sourced from @​fastly/js-compute's changelog.

3.33.1 (2025-03-12)

Fixed

• documentation fix (#1147) (15b9ea5)

3.33.0 (2025-03-12)

Added

• add support for EventTarget (#1145) (a735993)
• FormData support and Request.formData and Response.formData (#1144) (0214ae7)

Fixed

• Backend.prototype.health method definition (#1143) (42d429b)
• Weval stack overflow bug (#1135) (f6947d9)

3.32.2 (2025-02-26)

Fixed

• ready-based immediate task indexing (#1129) (8cfad4f)

3.32.1 (2025-02-20)

Fixed

• docs server toolchain fix (#1124) (c2490d1)

3.32.0 (2025-02-20)

Added

• Acl Support (#1073) (0f93f7b)

3.31.0 (2025-02-14)

Added

• KV store generation integer follow up (#1029) (#1108) (8a076da)

3.30.1 (2025-02-01)

Fixed

• docs build (#1104) (49b4758)

3.30.0 (2025-01-31)

... (truncated)

Commits

• 01cef44 chore(main): release 3.33.1 (#1148)
• 15b9ea5 fix: documentation fix (#1147)
• acfb8e0 chore(main): release 3.33.0 (#1139)
• a735993 feat: add support for EventTarget (#1145)
• 0214ae7 feat: FormData support and Request.formData and Response.formData (#1144)
• 42d429b fix: Backend.prototype.health method definition (#1143)
• 74e1602 chore(deps-dev): bump prismjs from 1.29.0 to 1.30.0 in /documentation (#1141)
• b834837 chore(deps): bump fast-check from 3.23.2 to 4.0.0 in /integration-tests/js-co...
• 6c09928 test: reenable config store tests (#1140)
• a6fc1d1 chore(deps): bump the npm group across 1 directory with 4 updates (#1138)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by harmony7, a new releaser for @​fastly/js-compute since your current version.

Updates @fastly/serve-vercel-build-output from 0.3.4 to 0.5.3

Changelog

Sourced from @​fastly/serve-vercel-build-output's changelog.

0.5.3 - 2024-04-10

Updated

• Workaround for crashing in doStep() for @​fastly/js-compute >= 3.0

0.5.2 - 2024-04-09

Fixed

• Include response headers from route matching (this includes those added by config files and middleware)
• Include correct headers in route errors

0.5.1 - 2023-11-08

Updated

• Apply "Compute" branding change.

0.5.0 - 2023-09-19

Added

• Patch server-side fetch() so that loopback requests are replaced with a call to serveRequest().

Updated

• Position @​fastly/js-compute as a devDependency and peerDependency.

0.4.1 - 2023-07-24

Updated

• Updated dependency libs

0.4.0 - 2023-07-04

Added

• Initial public release

Commits

• 567afc9 v0.5.3
• a638eda workaround: Avoid crashing during doStep while dumping requestContext in @​fas...
• 17bf308 Merge remote-tracking branch 'origin/main'
• f8f1423 v0.5.2
• 6134038 refactor: Send route matcher context to router error
• 62b6dbe fix: Serve response headers (not request!) when a router error occurs
• 49fb237 fix: Include response headers from route matching
• b17b979 Update LICENSE
• 5cbba48 v0.5.1
• c74af8d Merge pull request #2 from fastly/kats/branding-changes
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.