Registry / devops / esbuild-linux-arm

esbuild-linux-arm

library0.15.18jsnpmunverified

This package, `esbuild-linux-arm`, is a platform-specific binary component for esbuild, an extremely fast JavaScript and CSS bundler and minifier. The main `esbuild` package (currently at v0.28.0) automatically installs the correct platform-specific binary, making this package an indirect dependency for most users. esbuild is renowned for its exceptional speed, often performing builds 10 to 100 times faster than alternatives like Webpack or Rollup, attributed to its implementation in Go, extensive parallelism, and optimized algorithms. It maintains a sustainable and active release cadence, with frequent updates addressing bugs, introducing new features, and incorporating JavaScript specification changes. Key differentiators include its high performance, minimal configuration, built-in support for TypeScript and JSX transformation, and a growing plugin ecosystem.

devops

github ↗package ↗homepage ↗

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 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

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

While `require` works, esbuild encourages ESM for its API. The `build` function is the primary method for programmatically invoking esbuild. Asynchronous API is recommended, especially when using plugins.

import { build } from 'esbuild'

The `transform` function is used for processing individual code strings rather than entire file bundles. It's a named export, not a property of a default export.

import { transform } from 'esbuild'

Type imports should use `import type` to ensure they are stripped during compilation and do not introduce runtime dependencies.

import type { ServeOptions } from 'esbuild'

This quickstart demonstrates how to programmatically use esbuild's `build` API to bundle, minify, and create a sourcemap for a TypeScript entry file, targeting a Node.js environment.

import { build } from 'esbuild'; import path from 'path'; import url from 'url'; const __dirname = path.dirname(url.fileURLToPath(import.meta.url)); async function bundleCode() { try { await build({ entryPoints: [path.resolve(__dirname, 'src/index.ts')], bundle: true, minify: true, sourcemap: true, outfile: path.resolve(__dirname, 'dist/bundle.js'), platform: 'node', target: 'es2020', logLevel: 'info', }); console.log('Build successful: dist/bundle.js created.'); } catch (error) { console.error('Build failed:', error); process.exit(1); } } bundleCode(); // To make this runnable, create src/index.ts: // export function greet(name: string): string { // return `Hello, ${name}!`; // } // console.log(greet('esbuild user'));

Debug

Known footguns

breakingesbuild explicitly ships backwards-incompatible changes in minor versions (e.g., v0.27.0, v0.24.0, v0.23.0). It is crucial to pin exact versions or use only patch-level ranges (`~0.X.Y`) in `package.json` to prevent unexpected build failures upon upgrade.

gotchaWhen bundling for Node.js, `esbuild` does not automatically externalize Node.js built-in modules (like `fs`, `path`, `https`) by default unless `--platform=node` is explicitly set. Without this, it will attempt to bundle them, leading to errors like 'Could not resolve "https"'.

breakingesbuild's JavaScript API increased its minimum required Node.js version from 12 to 18 in a 2024 release. Running `esbuild` via its JS API on older Node.js versions will result in incompatibility errors.

gotchaesbuild treats TypeScript types as comments and strips them without performing type checking. This means type errors will not halt the esbuild process. It is recommended to enable the `isolatedModules` TypeScript compiler option.

breakingThe behavior of TypeScript parameter properties and class fields changed in v0.27.7, specifically regarding their lowering when the target environment does not support class fields. Previous versions might have incorrectly generated class fields, leading to runtime issues.

breakingSupport for macOS 10.15 Catalina was dropped in a 2024 release (v0.24.0) because the Go programming language (which esbuild is written in) dropped support for it. This affects users running older macOS versions.

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

ahrefsbot

script

googlebot

Resources

githubhttps://github.com/evanw/esbuild ↗

packagehttps://www.npmjs.com/package/esbuild-linux-arm ↗

homepagehttps://esbuild.github.io ↗