---
title: "@esbuild/android-x64 0.28.2: release notes, upgrades and advisories"
description: "@esbuild/android-x64 0.28.2: release notes, breaking changes by major version and no known security advisory."
url: https://inlinr.com/packages/@esbuild/android-x64
lang: en
---

[Packages](https://inlinr.com/packages)

# @esbuild/android-x64

0.28.2 · 8 Aug 2026 MIT 11.9M / week [Repository](https://github.com/evanw/esbuild) [Homepage](https://github.com/evanw/esbuild#readme) [npm](https://www.npmjs.com/package/@esbuild/android-x64) [Atom feed](https://inlinr.com/packages/feed/@esbuild/android-x64)

Your version 

## Latest releases

[All 113 releases](https://inlinr.com/packages/@esbuild/android-x64/releases)

1. 0.28.x · latest line
2. ### [0.28.2](https://inlinr.com/packages/@esbuild/android-x64/releases/0.28.2 "Open this release") [](https://github.com/evanw/esbuild/releases/tag/v0.28.2 "Read this release where it was published")  
8 Aug 2026

  - Fix tree shaking bug due to TypeScript import alias  
   This release fixes a bug that could cause esbuild to incorrectly tree-shake imports that are used in a TypeScript type alias under certain circumstances. Affected code uses a TypeScript-specific `import` assignment and looks something like this:  
  ```
  import Base from './dep.js';
  import Alias = Base.SomeType;
  ```
  - Fix CSS minification bug involving `&`  
   This release fixes a bug where esbuild's CSS minifier incorrectly removed a `&` when it was unsafe to do so. Here is an example:  
  ```
  /* Original code */
  .a .b {
    & .b:not(& .c) {
      color: red;
    }
  }
  /* Old output (with --minify) */
  .a .b{.b:not(& .c){color:red}}
  /* New output (with --minify) */
  .a .b{& .b:not(& .c){color:red}}
  ```
   This should match `<span class="a"><span class="b"><span class="b">yes</span></span></span>` but not `<span class="a"><span class="b">no</span></span>`. The old output incorrectly matched both.
  - Avoid overwriting input files without `--allow-overwrite`  
   For example: `esbuild input.js --outfile=input.js` tells esbuild to overwrite `input.js` with the output of running esbuild on it. This was supposed to already be prevented by default, but it accidentally regressed in version 0.17.0 and apparently didn't have any test coverage. The error message was being printed but the input file was still being overwritten. Oops.  
   This release puts the original behavior back. With this release, esbuild should now actually avoid overwriting input files unless `--allow-overwrite` is explicitly present. This is done by not writing out any files when a build error is encountered.
3. ### [0.28.1](https://inlinr.com/packages/@esbuild/android-x64/releases/0.28.1 "Open this release") [](https://github.com/evanw/esbuild/releases/tag/v0.28.1 "Read this release where it was published")  
11 Jun 2026

  - Security  
  Disallow `\` in local development server HTTP requests ([GHSA-g7r4-m6w7-qqqr](https://github.com/evanw/esbuild/security/advisories/GHSA-g7r4-m6w7-qqqr "https://github.com/evanw/esbuild/security/advisories/GHSA-g7r4-m6w7-qqqr"))  
   This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a `\` backslash character. It happened due to the use of Go's `path.Clean()` function, which only handles Unix-style `/` characters. HTTP requests with paths containing `\` are no longer allowed.
  - Security  
  Add integrity checks to the Deno API ([GHSA-gv7w-rqvm-qjhr](https://github.com/evanw/esbuild/security/advisories/GHSA-gv7w-rqvm-qjhr "https://github.com/evanw/esbuild/security/advisories/GHSA-gv7w-rqvm-qjhr"))  
   The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.  
   Note that esbuild's Deno API installs from `registry.npmjs.org` by default, but allows the `NPM_CONFIG_REGISTRY` environment variable to override this with a custom package registry. This change means that the esbuild executable served by `NPM_CONFIG_REGISTRY` must now match the expected content.
  - Avoid inlining `using` and `await using` declarations  
   Previously esbuild's minifier sometimes incorrectly inlined `using` and `await using` declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for `let` and `const` declarations by avoiding doing it for `var` declarations, which no longer worked when more declaration types were added. Here's an example:  
  ```
  // Original code
  {
    using x = new Resource()
    x.activate()
  }
  // Old output (with --minify)
  new Resource().activate();
  // New output (with --minify)
  {using e=new Resource;e.activate()}
  ```
4. ### [0.28.0](https://inlinr.com/packages/@esbuild/android-x64/releases/0.28.0 "Open this release") [](https://github.com/evanw/esbuild/releases/tag/v0.28.0 "Read this release where it was published")  
2 Apr 2026

  - Add support for `with { type: 'text' }` imports  
   The [import text](https://github.com/tc39/proposal-import-text "https://github.com/tc39/proposal-import-text") proposal has reached stage 3 in the TC39 process, which means that it's recommended for implementation. It has also already been implemented by [Deno](https://docs.deno.com/examples/importing%5Ftext/ "https://docs.deno.com/examples/importing_text/") and [Bun](https://bun.com/docs/guides/runtime/import-html "https://bun.com/docs/guides/runtime/import-html"). So with this release, esbuild also adds support for it. This behaves exactly the same as esbuild's existing [text loader](https://esbuild.github.io/content-types/#text "https://esbuild.github.io/content-types/#text"). Here's an example:  
  ```
  import string from './example.txt' with { type: 'text' }
  console.log(string)
  ```
  - Add integrity checks to fallback download path  
   Installing esbuild via npm is somewhat complicated with several different edge cases (see [esbuild's documentation](https://esbuild.github.io/getting-started/#additional-npm-flags "https://esbuild.github.io/getting-started/#additional-npm-flags") for details). If the regular installation of esbuild's platform-specific package fails, esbuild's install script attempts to download the platform-specific package itself (first with the `npm` command, and then with a HTTP request to `registry.npmjs.org` as a last resort).  
   This last resort path previously didn't have any integrity checks. With this release, esbuild will now verify that the hash of the downloaded binary matches the expected hash for the current release. This means the hashes for all of esbuild's platform-specific binary packages will now be embedded in the top-level `esbuild` package. Hopefully this should work without any problems. But just in case, this change is being done as a breaking change release.
  - Update the Go compiler from 1.25.7 to 1.26.1  
   This upgrade should not affect anything. However, there have been some significant internal changes to the Go compiler, so esbuild could potentially behave differently in certain edge cases:  
   You can read the [Go 1.26 release notes](https://go.dev/doc/go1.26 "https://go.dev/doc/go1.26") for more information.

Dependency tracking

## Know when your own dependencies move

@esbuild/android-x64 published 10 releases in the last 12 months. inlinr folds the routine ones into a line and keeps the few that need you.

- Advisories reach you  
An email when a critical or high advisory affects a project, before the next install.
- Upgrades checked first  
Peer ranges, Node, ESM-only and types changes read before you bump.
- Only what matters  
Majors and breaking notes stay; patches and sibling bumps fold into one line.

[How dependency tracking works](https://inlinr.com/dependencies)

## Security

No known security advisory.

## Health

[Details](https://inlinr.com/packages/@esbuild/android-x64/security#signals)

- **Provenance**:
- **Publisher**:
- **Maintainers**:
- **Scorecard**:
- **Size**:

## Weekly downloads

## Same family

- [esbuild 444.4M/wk](https://inlinr.com/packages/esbuild)
- [@esbuild/linux-x64 396.1M/wk](https://inlinr.com/packages/@esbuild/linux-x64)
- [@esbuild/linux-arm64 44.7M/wk](https://inlinr.com/packages/@esbuild/linux-arm64)
- [@esbuild/darwin-arm64 20.6M/wk](https://inlinr.com/packages/@esbuild/darwin-arm64)
- [@esbuild/win32-x64 18.9M/wk](https://inlinr.com/packages/@esbuild/win32-x64)
- [@esbuild/darwin-x64 15.1M/wk](https://inlinr.com/packages/@esbuild/darwin-x64)
- [@esbuild/win32-arm64 12.9M/wk](https://inlinr.com/packages/@esbuild/win32-arm64)
- [@esbuild/linux-loong64 12.3M/wk](https://inlinr.com/packages/@esbuild/linux-loong64)

Reading releases, release notes and advisories…

Registry facts last checked 20 Nov 2026\. Releases and advisories last read 20 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
