Registry / devops / esbuild-linux-ppc64le

esbuild-linux-ppc64le

library0.15.18jsnpmunverified

esbuild is an extremely fast, next-generation JavaScript and CSS bundler and minifier, written in Go. Its primary goal is to achieve significantly faster build times compared to other bundlers by leveraging parallel parsing, printing, and source map generation. The project maintains an active development pace with frequent releases, often including multiple minor or patch versions within weeks. As of its latest stable release, `esbuild` is at version 0.28.0. Key differentiators include its exceptional speed without requiring a cache, built-in support for JavaScript, CSS, TypeScript, and JSX, a straightforward API for CLI, JavaScript, and Go, and comprehensive features like ESM/CommonJS module bundling, tree shaking, minification, and source map generation. This specific package, `esbuild-linux-ppc64le`, provides the pre-compiled native binary for the Linux PowerPC 64-bit Little Endian architecture, which is an optional dependency automatically selected and installed by the main `esbuild` package based on the host system's platform and architecture.

devops

npm install esbuild-linux-ppc64le

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · ESBUILD-LINUX-PPC6

esbuild-linux-ppc64le

devopsjavascriptv0.15.18

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

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.

build

✓ import { build } from 'esbuild'

✗ const { build } = require('esbuild')

The `build` API is asynchronous and recommended for most bundling tasks. `esbuild` is primarily ESM-first, though CommonJS `require` still works.

transform

✓ import { transform } from 'esbuild'

✗ const { transform } = require('esbuild')

The `transform` API processes a single string of code without file system access, suitable for in-memory transpilation.

context

✓ import { context } from 'esbuild'

✗ import esbuild from 'esbuild'; esbuild.context

Since v0.17, `context` provides an incremental build API for faster rebuilds in development, supporting watch and serve modes. This should be explicitly imported.

This quickstart demonstrates how to use esbuild's `build` API to bundle a TypeScript application, including minification, source maps, and environment variable definition.

import { build } from 'esbuild'; const entryPoint = 'src/app.ts'; const outFile = 'dist/bundle.js'; async function bundleApp() { try { await build({ entryPoints: [entryPoint], bundle: true, minify: true, sourcemap: true, outfile: outFile, platform: 'node', target: 'es2022', // Define environment variables, e.g., for API keys define: { 'process.env.API_KEY': JSON.stringify(process.env.API_KEY ?? 'your-default-api-key'), }, logLevel: 'info', // Optional: watch mode for development // watch: { // onRebuild(error, result) { // if (error) console.error('watch build failed:', error); // else console.log('watch build succeeded:', result); // }, // }, }); console.log(`Successfully bundled ${entryPoint} to ${outFile}`); } catch (e) { console.error(`Bundling failed: ${e.message}`); process.exit(1); } } bundleApp();

esbuild --version

Debug

Known issues

breakingesbuild v0.27.0 introduced deliberate backwards-incompatible changes. Users are advised to pin exact versions or use patch-only version ranges (e.g., `^0.26.0` or `~0.26.0`) to avoid unexpected breakage from major or minor releases.

fix

Review release notes for v0.27.0 and subsequent versions before upgrading. Pin `esbuild` to an exact version in `package.json` (e.g., `"esbuild": "0.28.0"`) or use a tilde `~` prefix for patch-level updates (`"esbuild": "~0.28.0"`).

affects: >=0.27.0

gotchaUsing `--no-optional` flag with `npm install` can prevent esbuild from installing its platform-specific native binary, leading to errors when esbuild tries to execute. The native binaries are crucial for performance.

fix

Avoid using `--no-optional` when installing esbuild. Ensure npm can install optional dependencies. If issues persist, update npm to a recent version, as older npm versions might have had issues with `optionalDependencies`.

affects: >=0.6.0

gotchaThe `esbuild-wasm` package provides a cross-platform WebAssembly version of esbuild, but it is significantly slower (often 10x slower) than the native executables provided by the `esbuild` package and its platform-specific binary dependencies (like `esbuild-linux-ppc64le`).

fix

Always prefer installing the main `esbuild` package unless there's a specific need for the WebAssembly version (e.g., browser-based execution). The `esbuild` package will automatically select and install the correct native binary for your platform.

affects: >=0.8.0

gotchaEsbuild's CLI arguments can be subject to shell-specific behavior (e.g., glob expansion). For robust and predictable builds, especially when dealing with complex paths or patterns, using the JavaScript API is recommended.

fix

Transition from CLI usage to the JavaScript API (`esbuild.build()` or `esbuild.context()`) for projects requiring reliable and consistent build configurations across different environments.

affects: >=0.1.0

Errors

Common errors & fixes

Error: The package "esbuild-..." could not be found, and is needed by esbuild

This usually indicates that esbuild's optional platform-specific binary dependency could not be installed due to incompatible platform, architecture, or `--no-optional` flag during npm install.

fix

Remove `node_modules` and `package-lock.json`, then reinstall without `--no-optional`. Ensure your system's OS and architecture are supported by a native esbuild binary. Update npm if it's an older version.

npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for esbuild-linux-ppc64le@X.Y.Z: wanted {"os":"linux","arch":"ppc64"} (current: {"os":"darwin","arch":"x64"})

This warning occurs when npm attempts to install an architecture-specific esbuild binary that does not match the current operating system or CPU architecture. It often appears when running `npm install` on a different platform than where the lockfile was generated.

fix

This is typically a warning and not an error if the correct binary for the *current* platform is successfully installed. If it prevents esbuild from running, ensure `esbuild` is installed without `--no-optional` and that your `package-lock.json` doesn't exclusively lock to a non-matching platform. Delete `node_modules` and `package-lock.json` and reinstall to allow npm to choose the correct binary for the current system.

Error: Command failed: /path/to/node_modules/esbuild/bin/esbuild --version

This error means the esbuild executable could not be found or executed, often due to a missing binary, incorrect permissions, or an issue during installation.

fix

Check that the esbuild native binary is present in `node_modules/esbuild/bin/`. Verify its executable permissions. Try deleting `node_modules` and `package-lock.json` and running `npm install` again to ensure a clean installation. If using a custom install script, ensure it correctly handles esbuild's installation.

Upgrade

Version history

0.15.18latest on npm

Audit

Dependencies

esbuildoptionalThis package is an architecture-specific binary dependency for the main `esbuild` package, which orchestrates its use.

Agent activity

2 hits · last 30 days

node

Resources

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

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

homepagehttps://esbuild.github.io ↗