Skip to content

tools(deps): bump esbuild and vercel in /tools#1480

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/tools/multi-e158e22908
Open

tools(deps): bump esbuild and vercel in /tools#1480
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/tools/multi-e158e22908

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 6, 2026

Bumps esbuild to 0.27.0 and updates ancestor dependency vercel. These dependencies need to be updated together.

Updates esbuild from 0.14.47 to 0.27.0

Release notes

Sourced from esbuild's releases.

v0.27.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.26.0 or ~0.26.0. See npm's documentation about semver for more information.

  • Use Uint8Array.fromBase64 if available (#4286)

    With this release, esbuild's binary loader will now use the new Uint8Array.fromBase64 function unless it's unavailable in the configured target environment. If it's unavailable, esbuild's previous code for this will be used as a fallback. Note that this means you may now need to specify target when using this feature with Node (for example --target=node22) unless you're using Node v25+.

  • Update the Go compiler from v1.23.12 to v1.25.4 (#4208, #4311)

    This raises the operating system requirements for running esbuild:

    • Linux: now requires a kernel version of 3.2 or later
    • macOS: now requires macOS 12 (Monterey) or later

v0.26.0

  • Enable trusted publishing (#4281)

    GitHub and npm are recommending that maintainers for packages such as esbuild switch to trusted publishing. With this release, a VM on GitHub will now build and publish all of esbuild's packages to npm instead of me. In theory.

    Unfortunately there isn't really a way to test that this works other than to do it live. So this release is that live test. Hopefully this release is uneventful and is exactly the same as the previous one (well, except for the green provenance attestation checkmark on npm that happens with trusted publishing).

v0.25.12

  • Fix a minification regression with CSS media queries (#4315)

    The previous release introduced support for parsing media queries which unintentionally introduced a regression with the removal of duplicate media rules during minification. Specifically the grammar for @media <media-type> and <media-condition-without-or> { ... } was missing an equality check for the <media-condition-without-or> part, so rules with different suffix clauses in this position would incorrectly compare equal and be deduplicated. This release fixes the regression.

  • Update the list of known JavaScript globals (#4310)

    This release updates esbuild's internal list of known JavaScript globals. These are globals that are known to not have side-effects when the property is accessed. For example, accessing the global Array property is considered to be side-effect free but accessing the global scrollY property can trigger a layout, which is a side-effect. This is used by esbuild's tree-shaking to safely remove unused code that is known to be side-effect free. This update adds the following global properties:

    From ES2017:

    • Atomics
    • SharedArrayBuffer

    From ES2020:

    • BigInt64Array
    • BigUint64Array

    From ES2021:

    • FinalizationRegistry
    • WeakRef

    From ES2025:

    • Float16Array
    • Iterator

    Note that this does not indicate that constructing any of these objects is side-effect free, just that accessing the identifier is side-effect free. For example, this now allows esbuild to tree-shake classes that extend from Iterator:

    // This can now be tree-shaken by esbuild:

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2022

This changelog documents all esbuild versions published in the year 2022 (versions 0.14.11 through 0.16.12).

0.16.12

  • Loader defaults to js for extensionless files (#2776)

    Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

    • CLI:

      esbuild --bundle --loader:=css

    • JS:

      esbuild.build({
  bundle: true,
  loader: { '': 'css' },
})

    • Go:

      api.Build(api.BuildOptions{
  Bundle: true,
  Loader: map[string]api.Loader{"": api.LoaderCSS},
})

    In addition, the "type" field in package.json files now only applies to files with an explicit .js, .jsx, .ts, or .tsx extension. Previously it was incorrectly applied by esbuild to all files that had an extension other than .mjs, .mts, .cjs, or .cts including extensionless files. So for example an extensionless file in a "type": "module" package is now treated as CommonJS instead of ESM.

0.16.11

  • Avoid a syntax error in the presence of direct eval (#2761)

    The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

    // Original code
if (true) {
  function foo() {}
  console.log(!!foo)
  foo = null
  console.log(!!foo)
}

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for esbuild since your current version.


Updates vercel from 32.0.0 to 50.12.3

Release notes

Sourced from vercel's releases.

vercel@50.12.3

Patch Changes

vercel@50.12.2

Patch Changes

vercel@50.12.1

Patch Changes

  • Add support for VERCEL_TOKEN environment variable (#14831)

    The CLI now reads the VERCEL_TOKEN environment variable as an alternative to the --token flag. This allows for easier scripting and CI/CD integration without needing to pass the token as a command-line argument.

    The --token flag takes precedence over the environment variable when both are provided.

  • Fix vc link --repo in git worktree (#14867)

  • Simplify CLI update prompt to yes/no confirmation with changelog link in body (#14885)

  • Updated dependencies [df1d02d5257e33dc10640b20eea1c1e59c5842cf, e558a1657f5aa43048cde0f3b97bead7c9bf1070]:

    • @​vercel/next@​4.15.23

... (truncated)

Changelog

Sourced from vercel's changelog.

50.12.3

Patch Changes

50.12.2

Patch Changes

50.12.1

Patch Changes

  • Add support for VERCEL_TOKEN environment variable (#14831)

    The CLI now reads the VERCEL_TOKEN environment variable as an alternative to the --token flag. This allows for easier scripting and CI/CD integration without needing to pass the token as a command-line argument.

    The --token flag takes precedence over the environment variable when both are provided.

  • Fix vc link --repo in git worktree (#14867)

  • Simplify CLI update prompt to yes/no confirmation with changelog link in body (#14885)

... (truncated)

Commits

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 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.

@dependabot
tools(deps): bump esbuild and vercel in /tools
16f3102 
Bumps [esbuild](https://github.com/evanw/esbuild) to 0.27.0 and updates ancestor dependency [vercel](https://github.com/vercel/vercel/tree/HEAD/packages/cli). These dependencies need to be updated together.


Updates `esbuild` from 0.14.47 to 0.27.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2022.md)
- [Commits](evanw/esbuild@v0.14.47...v0.27.0)

Updates `vercel` from 32.0.0 to 50.12.3
- [Release notes](https://github.com/vercel/vercel/releases)
- [Changelog](https://github.com/vercel/vercel/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/vercel/vercel/commits/vercel@50.12.3/packages/cli)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.27.0
  dependency-type: indirect
- dependency-name: vercel
  dependency-version: 50.12.3
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added scope: deps An issue related to dependencies. scope: inventory An issue related to auxiliary code, e.g. CI config, Makefiles, etc. type: improvement A new improvement proposal. labels Feb 6, 2026
@vercel
Copy link

vercel bot commented Feb 6, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tact Error Error Feb 6, 2026 8:23am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kamilsk kamilsk kamilsk approved these changes

Assignees

No one assigned

Labels

scope: deps An issue related to dependencies. scope: inventory An issue related to auxiliary code, e.g. CI config, Makefiles, etc. type: improvement A new improvement proposal.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@kamilsk