Registry / devops / esbuild-android-arm64

esbuild-android-arm64

JSON →
library0.15.18jsnpmunverified

This package provides the pre-compiled Android ARM 64-bit binary for esbuild, a high-performance JavaScript bundler and minifier. It is primarily consumed as an optional platform-specific dependency by the main `esbuild` npm package, which automatically selects and utilizes the appropriate binary for the host system. The overarching `esbuild` project is actively maintained with frequent releases, often including multiple patch versions per month and minor versions every few months, ensuring rapid bug fixes and feature enhancements. It is renowned for its exceptional speed, achieved by being written in Go and compiling to native code, distinguishing it significantly from JavaScript-based bundlers such as Webpack or Rollup. The current stable version for the main `esbuild` project is 0.28.0. This specific package, `esbuild-android-arm64`, does not expose any direct JavaScript API; its sole purpose is to supply the underlying executable for environments targeting Android ARM 64-bit architectures.

devops
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

This package (`esbuild-android-arm64`) provides a platform-specific binary and does not expose direct JavaScript imports. The `build` function is imported from the main `esbuild` package. The `esbuild` API is primarily designed for ESM; while CommonJS `require` may work for older versions or specific setups, ESM is the recommended approach for modern Node.js and TypeScript projects. Type definitions are shipped with the package.

import { build } from 'esbuild'

The `transform` function is imported from the main `esbuild` package and is used for single-file transformations without bundling. Same ESM/CJS considerations as `build` apply.

import { transform } from 'esbuild'

The `Plugin` interface is imported from the main `esbuild` package. It is used for type hinting when creating custom esbuild plugins and is not a runtime value. Use `import type` for type-only imports in TypeScript to avoid bundling unused imports.

import type { Plugin } from 'esbuild'

This quickstart demonstrates a basic esbuild configuration to bundle a TypeScript application, including generating source maps, minifying code, targeting specific environments, and incorporating a simple custom plugin for build lifecycle logging. This code leverages the main `esbuild` package, which utilizes this binary.

import { build } from 'esbuild'; import path from 'path'; import process from 'process'; // Define your entry point and output file paths const entryPoint = path.resolve(process.cwd(), 'src/index.ts'); const outFile = path.resolve(process.cwd(), 'dist/bundle.js'); async function runBuild() { try { // Configure and run the esbuild bundling process await build({ entryPoints: [entryPoint], bundle: true, // Enable bundling outfile: outFile, // Specify the output file platform: 'node', // Target Node.js environment format: 'esm', // Output ES Module format sourcemap: true, // Generate source maps minify: true, // Enable minification target: ['es2020', 'node18'], // Target JavaScript and Node.js versions define: { 'process.env.NODE_ENV': '"production"' }, // Define global variables plugins: [ // Example of a simple esbuild plugin logging build events { name: 'my-build-logger', setup(build) { build.onStart(() => { console.log('esbuild process started...'); }); build.onEnd(result => { if (result.errors.length > 0) { console.error('esbuild finished with errors:', result.errors); } else { console.log('esbuild finished successfully!'); } }); } } ] }); console.log(`Application bundled to ${outFile}`); } catch (error) { console.error('esbuild failed during build:', error); process.exit(1); } } runBuild();
Debug
Known footguns
breakingesbuild `v0.27.0` introduced deliberate backwards-incompatible changes. Relying on caret (`^`) or tilde (`~`) ranges for `esbuild` may lead to unexpected behavior. It is strongly recommended to pin the exact version (`0.x.y`) in `package.json` or use `~0.x.y` to limit updates to patch releases.
gotchaIn esbuild `v0.27.6`, TypeScript parameter properties were incorrectly generated as class fields even when the configured target environment did not support them, potentially leading to runtime errors in older environments. This was fixed in `v0.27.7`.
gotchaesbuild versions `0.25.11` through `0.27.3` introduced regressions in parsing and minifying specific CSS media query syntaxes (e.g., `<media-type> and <media-condition-without-or>`). This could lead to incorrect output or failed minification.
gotchaesbuild versions prior to `v0.27.1` had a bug where `var` declarations nested inside `if` statements in ES modules imported via `require` (which are wrapped) might not be hoisted correctly, leading to runtime errors.
gotchaAs of `v0.26.0`, esbuild packages are published using GitHub's trusted publishing. While this enhances supply chain security by leveraging automated workflows for package publication, it represents a change in the distribution mechanism.
Upgrade
Version history

Breaking-change detection hasn't run for this library yet.

Audit
Security & dependencies

CVE tracking and dependency tree are planned for a later release.

Agent activity
10 hits · last 30 days
gptbot
4
ahrefsbot
4
script
1
googlebot
1
Resources