esbuild Linux 32-bit Binary

0.15.18 · active · verified Sun Apr 19

This package provides the precompiled 32-bit Linux binary for esbuild, a high-performance JavaScript/TypeScript bundler and minifier implemented in Go. As a component of the broader esbuild ecosystem, `esbuild-linux-32` is typically an optional or direct dependency of the main `esbuild` npm package, which dynamically loads the appropriate binary for the host system. The main `esbuild` project is actively maintained, with frequent releases (often weekly or bi-weekly) addressing new web standards, bug fixes, and performance enhancements. Its current stable version is around `0.28.x`. This specific package is crucial for users deploying esbuild on 32-bit Linux environments, ensuring native performance by providing the architecture-specific executable.

Common errors

```
Error: esbuild: No matching binary found for linux/ia32. You might need to install "esbuild-linux-32" manually, or you might have a broken installation.
```
cause The main `esbuild` package could not automatically find or load the appropriate binary for the detected operating system and architecture (Linux 32-bit).

fix Ensure that `esbuild-linux-32` is correctly installed as a dependency. If it's a direct dependency, verify its presence in `node_modules`. If using the main `esbuild` package, `npm install esbuild --save-dev` or `yarn add esbuild --dev` should handle optional dependencies, but manual intervention might be needed: `npm install esbuild-linux-32 --save-dev`.
```
Error: Cannot find module 'esbuild' from '...' at Function.Module._resolveFilename (node:internal/modules/cjs/loader:940:15)
```
cause This specific package (`esbuild-linux-32`) is a binary, not the primary JavaScript API for esbuild. The `esbuild` module itself is not found.

fix To use esbuild programmatically, you must install and import the main `esbuild` npm package, which then leverages this binary internally. Install it via `npm install esbuild` or `yarn add esbuild` and import `import * as esbuild from 'esbuild'`.

Warnings

breaking esbuild v0.27.0 introduced backwards-incompatible changes. While the specific impact on the binary itself is minimal, consuming packages (like the main `esbuild` npm package) might require explicit version pinning (`^0.26.0` or `~0.26.0`) to avoid automatically picking up unexpected updates.
Fix: It is highly recommended to pin the exact version of `esbuild` in your `package.json` (e.g., `"esbuild": "0.28.0"`) or use a caret range that only accepts patch updates (e.g., `"esbuild": "^0.28.0"`) to prevent automatic upgrades to major or minor versions that could introduce breaking changes.
gotcha esbuild's default `platform` option changed from `node` to `browser` in version 0.19.0. This can affect how Node.js built-in modules (like `path`, `fs`) are handled, often leading to errors if not explicitly configured for a Node.js target.
Fix: If bundling for a Node.js environment, explicitly set the `platform` option to `'node'` in your esbuild configuration: `await esbuild.build({ ..., platform: 'node' })`.
gotcha esbuild has a strong opinion on file extensions and module types. Incorrectly configuring `jsxFactory`, `jsxFragment`, or `tsconfig.json` paths can lead to compilation errors or unexpected runtime behavior, especially with frameworks like React.
Fix: Ensure your `tsconfig.json` (if used) is correctly configured, especially `jsxFactory`, `jsxFragment`, and `paths`. For example, `"jsxFactory": "React.createElement"` and `"jsxFragment": "React.Fragment"`. Alternatively, pass these options directly to esbuild: `await esbuild.build({ ..., jsxFactory: 'h', jsxFragment: 'Fragment' })`.

Install

npm install esbuild-linux-32 npm
yarn add esbuild-linux-32 yarn
pnpm add esbuild-linux-32 pnpm

view raw JSON →