{"id":16018,"library":"esbuild-windows-32","title":"esbuild Windows 32-bit Binary","description":"esbuild-windows-32 is a platform-specific package containing the Windows 32-bit executable for esbuild. Esbuild is an extremely fast, modern JavaScript and CSS bundler and minifier written in Go. Its primary differentiator is its exceptional speed, often performing 10-100 times faster than traditional bundlers like Webpack or Rollup, attributed to its native Go implementation, heavy use of parallelism, and optimized memory access patterns. The current stable version of the core `esbuild` package is `0.28.0`, released in early April 2026. The project maintains a sustainable and active release cadence, with new versions typically published at least once every three months, reflecting ongoing development and improvements. Key features include built-in support for JavaScript, TypeScript, JSX, and CSS, comprehensive bundling of ESM and CommonJS modules, aggressive tree-shaking and minification, source map generation, a straightforward API for CLI, JavaScript, and Go, and a flexible plugin system. It's widely adopted and integrated into tools like Vite, Angular (v17+), and Ruby on Rails (v7+). This `esbuild-windows-32` package is an optional dependency for the main `esbuild` package, automatically installed by npm based on the detected operating system and architecture.","status":"active","version":"0.15.18","language":"javascript","source_language":"en","source_url":"https://github.com/evanw/esbuild","tags":["javascript"],"install":[{"cmd":"npm install esbuild-windows-32","lang":"bash","label":"npm"},{"cmd":"yarn add esbuild-windows-32","lang":"bash","label":"yarn"},{"cmd":"pnpm add esbuild-windows-32","lang":"bash","label":"pnpm"}],"dependencies":[],"imports":[{"note":"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.","wrong":"const esbuild = require('esbuild'); esbuild.build(...)","symbol":"build","correct":"import { build } from 'esbuild'"},{"note":"Used for incremental builds or watch mode. Introduced in `esbuild` v0.14.0. Always a named import from the top-level `esbuild` package.","wrong":"import esbuild from 'esbuild'; esbuild.context(...)","symbol":"context","correct":"import { context } from 'esbuild'"},{"note":"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.","wrong":"require('esbuild').transformSync(...)","symbol":"transform","correct":"import { transform } from 'esbuild'"}],"quickstart":{"code":"import { build } from 'esbuild';\nimport path from 'path';\n\nconst projectRoot = process.cwd();\nconst entryPoint = path.join(projectRoot, 'src', 'index.ts');\nconst outputDir = path.join(projectRoot, 'dist');\n\nasync function bundleApp() {\n  try {\n    await build({\n      entryPoints: [entryPoint],\n      bundle: true,\n      minify: true,\n      sourcemap: true,\n      platform: 'node',\n      format: 'esm',\n      outdir: outputDir,\n      target: ['node18', 'es2022'],\n      define: { 'process.env.NODE_ENV': '\"production\"' },\n      logLevel: 'info',\n    });\n    console.log('Build successful!');\n  } catch (error) {\n    console.error('Build failed:', error);\n    process.exit(1);\n  }\n}\n\nbundleApp();","lang":"typescript","description":"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."},"warnings":[{"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`.","message":"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.","severity":"breaking","affected_versions":">=0.17.0"},{"fix":"Upgrade your Node.js environment to version 18 or newer.","message":"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.","severity":"breaking","affected_versions":">=0.24.0"},{"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.","message":"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.","severity":"breaking","affected_versions":"=0.27.0"},{"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.","message":"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.","severity":"breaking","affected_versions":"=0.28.0"},{"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.","message":"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.","severity":"gotcha","affected_versions":">=0.20.0"}],"env_vars":null,"last_verified":"2026-04-21T00:00:00.000Z","next_check":"2026-07-20T00:00:00.000Z","problems":[{"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.","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.","error":"Error: EACCES: permission denied, unlink 'node_modules/esbuild/bin/esbuild'"},{"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`.","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.","error":"esbuild: command not found"},{"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.","cause":"You are attempting to use a recent version of `esbuild` with an outdated Node.js environment.","error":"The esbuild JavaScript API is not supported on node versions < 18.0.0"},{"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.","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.","error":"Error: Could not resolve \"./my-module\" (use \"--bundle\" to enable this)"},{"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.","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).","error":"SyntaxError: Cannot use import statement outside a module"}],"ecosystem":"npm"}