Registry / devops / esbuild-windows-64

esbuild-windows-64

library0.15.18jsnpmunverified

esbuild-windows-64 is an optional platform-specific package providing the native 64-bit Windows executable for esbuild. esbuild itself is an extremely fast JavaScript and CSS bundler and minifier, written in Go to achieve superior performance compared to traditional JavaScript-based bundlers like Webpack or Rollup, often boasting 10-100x faster build times. It processes JavaScript, CSS, TypeScript, and JSX, offering features like tree shaking, minification, source maps, a local development server, and watch mode. The current stable version of esbuild is 0.28.0, with frequent patch releases and occasional minor versions introducing breaking changes. This package is typically installed automatically as a dependency of the main `esbuild` package and is not intended for direct user interaction or programmatic imports.

devops

github ↗package ↗homepage ↗

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.

For ESM projects, use named imports like `import * as esbuild from 'esbuild';`. The CommonJS `require` style is still supported but ESM is generally preferred for new Node.js projects. This package (`esbuild-windows-64`) is *not* directly imported.

import * as esbuild from 'esbuild'; await esbuild.build({...});

The `context` API is used for watch and serve modes, providing a long-running process for incremental builds. It's an asynchronous function.

import { context } from 'esbuild'; const ctx = await context({...});

The `transform` API is for transforming a single string of code without bundling. Useful for integrating esbuild into other tools or for quick code manipulations.

import { transform } from 'esbuild'; const result = await transform(code, {...});

This quickstart demonstrates how to programmatically use esbuild's `build` API to bundle and minify a TypeScript application targeting Node.js, including JSX transformation and sourcemap generation.

import * as esbuild from 'esbuild'; import path from 'path'; import { fileURLToPath } from 'url'; const __dirname = path.dirname(fileURLToPath(import.meta.url)); const entryPoint = path.join(__dirname, 'src', 'app.ts'); const outputDir = path.join(__dirname, 'dist'); const config = { entryPoints: [entryPoint], bundle: true, minify: true, sourcemap: true, outfile: path.join(outputDir, 'bundle.js'), platform: 'node', // or 'browser', 'neutral' format: 'esm', // or 'cjs', 'iife' target: 'es2020', logLevel: 'info', jsx: 'automatic', external: ['react', 'react-dom'] // Example: exclude external packages }; async function buildProject() { try { await esbuild.build(config); console.log('Build successful!'); } catch (error) { console.error('Build failed:', error); process.exit(1); } } buildProject();

Debug

Known footguns

breakingesbuild v0.27.0 introduced backwards-incompatible changes, specifically with the use of `Uint8Array.fromBase64` for binary loading. Projects pinning older versions or using broad semver ranges might encounter issues if this new API is not available in their target environment.

breakingesbuild v0.28.0 introduced integrity checks to fallback binary download paths. While enhancing security, this was a breaking change. Additionally, an update to the Go compiler might lead to subtle behavioral differences in edge cases due to changes in garbage collection, memory allocation, and executable format.

gotchaCopying `node_modules` directories between different operating systems or architectures (e.g., Windows to Linux Docker, macOS x86-64 to ARM via Rosetta) will cause `esbuild` to fail because it installs platform-specific native binaries. The `esbuild-windows-64` package is one such binary.

gotchaInstalling `esbuild` with `--omit=optional` or `--no-optional` flags can prevent the platform-specific binary (like `esbuild-windows-64`) from being correctly installed, leading to the `node_modules/.bin/esbuild` command being missing or non-functional.

gotchaWhile `esbuild-wasm` offers a cross-platform solution, it comes with a significant performance cost, often being 10 times slower than the native `esbuild` package. Using `esbuild-wasm` as a general solution for native performance issues is not recommended.

Upgrade

Version history

Breaking-change detection hasn't run for this library yet.

Audit

Security & dependencies

CVE tracking and dependency tree are planned for a later release.

Agent activity

10 hits · last 30 days

gptbot

ahrefsbot

script

googlebot

Resources

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

packagehttps://www.npmjs.com/package/esbuild-windows-64 ↗

homepagehttps://esbuild.github.io ↗