This package, `esbuild-linux-64`, provides the native 64-bit Linux binary for esbuild, an extremely fast JavaScript and CSS bundler and minifier. Esbuild is renowned for its exceptional speed, often completing builds 10-100 times faster than alternatives like Webpack or Rollup, attributed to its implementation in Go and heavy use of parallelism. It supports modern JavaScript features, TypeScript, JSX, tree-shaking, and has a simple, intuitive API. While `esbuild-linux-64` itself is a low-level component, the overarching `esbuild` project (currently at v0.28.0 as of April 2026) maintains a very active release cadence, frequently publishing updates with new features, bug fixes, and performance improvements. It is widely adopted by tools like Vite, Angular (since v17), and Ruby on Rails (since v7) for its performance. The package's purpose is to be an automatically selected optional dependency of the main `esbuild` package, providing the correct native executable for Linux x64 environments.
npm install esbuild-linux-64Verified import paths — ran on the pinned version, not inferred.
Demonstrates a basic esbuild bundling and minification process using its JavaScript API, highlighting how the main `esbuild` package abstracts away platform-specific binaries like `esbuild-linux-64`.
Pin the `esbuild` package version in `package.json` (e.g., `"esbuild": "0.28.0"`) or use `~` for patch updates (e.g., `"esbuild": "~0.28.0"`). Regularly review the changelog before upgrading.
Ensure `npm install` runs within the target environment (e.g., inside the Docker container), rather than copying `node_modules` from a different OS/architecture. Add `node_modules` to `.dockerignore`. Alternatively, consider `esbuild-wasm` for full platform portability, though with a performance penalty.
Ensure your Node.js environment is version 18 or later. Update Node.js if necessary. The `engines` field `"node": ">=12"` in `esbuild-linux-64`'s `package.json` may be outdated or refer to older core compatibility.
When bundling for Node.js (`--platform=node`), generally use `--format=cjs` for maximum compatibility with npm packages. If using ESM, be aware of Node.js's CJS/ESM interoperability limitations and potential need for polyfills for features like top-level await.
Ensure the underlying Linux operating system meets the minimum kernel version requirements. For specific `Uint8Array.fromBase64` usage with Node, you might need to specify a target like `--target=node22` if not on Node v25+.
Remove `node_modules` and `package-lock.json` (or `yarn.lock`) and run `npm install` (or `yarn install`) directly within the target environment (e.g., inside the Docker container). Make sure `node_modules` is excluded from copy operations in your deployment pipeline.
Import `esbuild` instead of `esbuild-linux-64`. The main `esbuild` package dynamically loads the correct platform-specific binary. For example: `import { build } from 'esbuild';`.Ensure `esbuild` (the main package) is installed correctly, typically as a `devDependency`. Use `npx esbuild` to run the local CLI, or ensure `$(npm bin)` is in your PATH. If `esbuild-linux-64` was installed standalone, it won't provide the `esbuild` CLI command directly, you need the main `esbuild` package.
Adjust the `--target` option in your esbuild configuration (e.g., `--target=es2022` or `--target=node18`) to match your intended runtime environment. Ensure your Node.js version meets esbuild's minimum requirements, especially for recent features.
No dependency data recorded yet.