esbuild Windows 32-bit Binary

Common errors

• Error: EACCES: permission denied, unlink 'node_modules/esbuild/bin/esbuild'

  cause Insufficient permissions to delete or modify the esbuild binary during installation or update, often on Windows systems or due to global npm cache issues.
  fix Try running `npm cache clean --force` and then `npm install esbuild` again. On Windows, ensure your terminal is running with administrator privileges, or try deleting `node_modules` and `package-lock.json` before reinstalling.

• esbuild: command not found

  cause The esbuild binary was not correctly installed, or its path is not in your system's PATH environment variable, or npm's `postinstall` script failed to link it properly.
  fix Ensure `esbuild` is listed in your `package.json` and try `npm install` again. If the issue persists, check npm logs for `postinstall` script failures or manually verify the binary exists in `node_modules/esbuild/bin/esbuild`.

• The esbuild JavaScript API is not supported on node versions < 18.0.0

  cause You are attempting to use a recent version of `esbuild` with an outdated Node.js environment.
  fix Upgrade your Node.js runtime to version 18.0.0 or higher. You can use tools like `nvm` (Node Version Manager) to easily switch Node.js versions.

• Error: Could not resolve "./my-module" (use "--bundle" to enable this)

  cause You are trying to import a module that esbuild cannot find in standalone transformation mode. The error explicitly indicates that bundling is required for module resolution.
  fix Add the `bundle: true` option to your esbuild configuration or `--bundle` flag if using the CLI, to enable esbuild's module resolution and bundling capabilities.

• SyntaxError: Cannot use import statement outside a module

  cause This error typically occurs when a JavaScript file using ESM `import`/`export` syntax is being run in a CommonJS context (e.g., a `.js` file without `"type": "module"` in `package.json`, or an older Node.js version).
  fix Ensure your project's `package.json` includes `"type": "module"` for ESM files, or explicitly name your ESM files with a `.mjs` extension. Alternatively, configure esbuild's `format` option (e.g., `format: 'cjs'`) to output CommonJS compatible code.

Warnings

• breaking Esbuild releases frequently include backwards-incompatible changes. It is highly recommended to pin the exact version of `esbuild` in `package.json` (e.g., `"esbuild": "0.28.0"`) or use a caret range that only accepts patch upgrades (e.g., `^0.28.0`) to avoid unexpected breakages, especially for major/minor version bumps.
  Fix: Update your `package.json` to pin `esbuild` to an exact version or use a patch-level semver range, then run `npm install` or `yarn install`.
• breaking Starting with versions released in 2024 (roughly `v0.24.0` and above), `esbuild` increased its minimum required Node.js version for its JavaScript API from Node 12 to Node 18. Running `esbuild` on older Node.js versions will result in errors due to an incompatibility with Go-generated JavaScript for the `esbuild-wasm` package.
  Fix: Upgrade your Node.js environment to version 18 or newer.
• breaking Esbuild v0.27.0 introduced deliberate backwards-incompatible changes, including conditional use of `Uint8Array.fromBase64` if available, with a fallback. This might cause subtle behavioral differences in environments where this function's availability varies.
  Fix: Review your build output and ensure compatibility if your target environment relies on specific `Uint8Array` behavior. Consider testing thoroughly after upgrading to this version.
• breaking Esbuild v0.28.0 introduced integrity checks for fallback binary downloads and updated the Go compiler. While the Go compiler update is not expected to cause issues, it could potentially affect edge cases. The integrity checks are a security improvement.
  Fix: No direct fix is usually needed, but be aware of the update. If encountering new, unexpected behavior, consult the esbuild GitHub releases for Go compiler changes in v0.28.0.
• gotcha When `esbuild` generates build metadata (metafiles), large JSON output can hit V8's implementation-specific maximum string length limit, causing `JSON.parse` to fail when accessing the metafile object via the JavaScript API.
  Fix: If working with extremely large projects that generate huge metafiles, consider writing the metafile to a file and processing it with a streaming JSON parser or external tools, rather than directly relying on the in-memory JavaScript API return value.

Install

• npm install esbuild-windows-32 npm
• yarn add esbuild-windows-32 yarn
• pnpm add esbuild-windows-32 pnpm

Imports

• build
  wrong:

  const esbuild = require('esbuild'); esbuild.build(...)

  correct:

  import { build } from 'esbuild'

  This package (`esbuild-windows-32`) is an internal binary. Users typically interact with the main `esbuild` package, which dynamically loads the correct platform-specific binary. Named imports are standard for the `build` function.
• context
  wrong:

  import esbuild from 'esbuild'; esbuild.context(...)

  correct:

  import { context } from 'esbuild'

  Used for incremental builds or watch mode. Introduced in `esbuild` v0.14.0. Always a named import from the top-level `esbuild` package.
• transform
  wrong:

  require('esbuild').transformSync(...)

  correct:

  import { transform } from 'esbuild'

  The `transform` function (and `transformSync`) is for transforming a single string of code without bundling. It's a named import. While `transformSync` exists, the async `transform` is generally preferred for performance in Node.js environments.

Quickstart

This quickstart demonstrates a basic esbuild setup to bundle a TypeScript application for Node.js, including minification, sourcemaps, and target environment configuration. The `esbuild-windows-32` binary is used automatically by the `esbuild` package on compatible Windows 32-bit systems.

import { build } from 'esbuild';
import path from 'path';

const projectRoot = process.cwd();
const entryPoint = path.join(projectRoot, 'src', 'index.ts');
const outputDir = path.join(projectRoot, 'dist');

async function bundleApp() {
  try {
    await build({
      entryPoints: [entryPoint],
      bundle: true,
      minify: true,
      sourcemap: true,
      platform: 'node',
      format: 'esm',
      outdir: outputDir,
      target: ['node18', 'es2022'],
      define: { 'process.env.NODE_ENV': '"production"' },
      logLevel: 'info',
    });
    console.log('Build successful!');
  } catch (error) {
    console.error('Build failed:', error);
    process.exit(1);
  }
}

bundleApp();