esbuild Linux MIPS64LE Native Binary

Common errors

• Error: No matching esbuild binary found for this platform.

  cause The esbuild JavaScript wrapper could not find or execute its corresponding native binary for the detected operating system and architecture.
  fix Ensure you have installed the main `esbuild` package, allowing it to select the correct platform-specific binary. If cross-compiling or using a non-standard environment, verify that the correct `esbuild-xxx-yyy` package is installed and accessible, or specify the binary path via environment variables.

• ReferenceError: require is not defined in ES module scope

  cause Attempting to use CommonJS `require()` syntax in a JavaScript file that Node.js or esbuild is interpreting as an ES Module.
  fix For ES Modules, use `import` statements instead of `require()`. Ensure your `package.json` has `"type": "module"` if you intend for `.js` files to be ESM, or configure esbuild's `format` option (e.g., `esm` or `cjs`) to match your target environment. Conversely, if targeting CJS, avoid top-level `import` statements.

• Could not resolve 'module-name'

  cause esbuild failed to locate an imported module, often due to a missing `node_modules` dependency, an incorrect relative path, or an unconfigured path alias.
  fix Verify that the dependency is installed (`npm install module-name` or `yarn add module-name`). Check the import path for correctness. If using path aliases (e.g., in `tsconfig.json`), ensure esbuild is configured to interpret them, potentially via an esbuild plugin or by pointing esbuild to your `tsconfig.json`.

Warnings

• breaking esbuild v0.27.0 introduced deliberate backwards-incompatible changes. To prevent unexpected build failures or behavior, it is strongly recommended to pin the exact version of `esbuild` in your `package.json` (e.g., `"esbuild": "0.20.24"`) or use a patch-only version range (`~0.20.0`).
  Fix: Update your `package.json` to pin `esbuild` to an exact version or use a `~X.Y.Z` version range. Review the esbuild changelog for detailed migration steps for new major versions.
• gotcha This package (`esbuild-linux-mips64le`) is a platform-specific native binary. Users should typically install the main `esbuild` package, which automatically detects and installs the correct binary for the host system. Directly installing this package is only for specific cross-compilation or advanced use cases and can lead to 'No matching esbuild binary found' errors if installed on an incompatible platform.
  Fix: For most users, `npm install esbuild` or `yarn add esbuild` is sufficient. Let the main `esbuild` package manage the installation of the appropriate platform-specific binary for your environment.
• gotcha esbuild's JavaScript wrapper requires Node.js version 12 or higher. Attempting to run esbuild with older Node.js versions may result in execution errors or unexpected behavior.
  Fix: Upgrade your Node.js environment to version 12 or newer. The `nvm` (Node Version Manager) utility is recommended for easily managing multiple Node.js versions.

Install

• npm install esbuild-linux-mips64le npm
• yarn add esbuild-linux-mips64le yarn
• pnpm add esbuild-linux-mips64le pnpm

Imports

• build
  wrong:

  const { build } = require('esbuild')

  correct:

  import { build } from 'esbuild'

  The `build` API is asynchronous and is the primary entry point for bundling files. While `require` works, ESM `import` is the idiomatic modern approach.
• transform
  wrong:

  const esbuild = require('esbuild'); esbuild.transform(code)

  correct:

  import { transform } from 'esbuild'

  The `transform` API is used for processing individual code strings or files without full bundling, often for runtime compilation or server-side rendering.
• formatMessages
  wrong:

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

  correct:

  import { formatMessages } from 'esbuild'

  Used to format diagnostic messages (errors or warnings) returned by esbuild's build or transform operations into human-readable strings.

Quickstart

Demonstrates a basic esbuild bundling operation, compiling a TypeScript entry point with a utility module into a single JavaScript file, with minification and sourcemaps toggled by NODE_ENV.

import { build } from 'esbuild';
import path from 'node:path';
import process from 'node:process';
import { writeFileSync, mkdirSync } from 'node:fs';

const entryPoint = 'src/index.ts';
const outputDir = 'dist';
const outputFileName = 'bundle.js';

// Create dummy entry points for the quickstart
mkdirSync('src', { recursive: true });
writeFileSync(entryPoint, `
import { add } from './utils';

console.log('Hello from esbuild!');
console.log('2 + 3 =', add(2, 3));
`);
writeFileSync('src/utils.ts', `
export function add(a: number, b: number): number {
  return a + b;
}
`);

async function runBuild() {
  try {
    await build({
      entryPoints: [entryPoint],
      bundle: true,
      minify: process.env.NODE_ENV === 'production',
      sourcemap: process.env.NODE_ENV !== 'production',
      outfile: path.join(outputDir, outputFileName),
      platform: 'node', // Can be 'browser', 'node', or 'neutral'
      target: 'es2022',
      logLevel: 'info',
      // Example plugin usage:
      // plugins: [{
      //   name: 'example',
      //   setup(build) {
      //     build.onResolve({ filter: /\./ }, args => {
      //       if (args.path === 'foo') return { path: args.path, namespace: 'foo-ns' };
      //     });
      //     build.onLoad({ filter: /foo/, namespace: 'foo-ns' }, () => ({
      //       contents: 'export default "bar";',
      //       loader: 'js',
      //     }));
      //   },
      // }],
    });
    console.log(`Build successful: ${path.join(outputDir, outputFileName)}`);
  } catch (e) {
    console.error('Build failed:', e);
    process.exit(1);
  }
}

runBuild();