This package provides the `illumos 64-bit` native executable for esbuild, a high-performance JavaScript bundler and minifier. Esbuild, currently at version `0.28.0` as of early April 2026, is renowned for its exceptional speed, largely due to its implementation in Go, making it significantly faster than bundlers written in JavaScript. It offers capabilities for bundling JavaScript, TypeScript, JSX, TSX, CSS, and image files, supporting both ESM and CommonJS formats. The project maintains a rapid release cadence, with frequent patch updates and minor versions typically released every few months, addressing bugs, introducing new features, and enhancing performance. It differentiates itself through its aggressive performance focus, minimal configuration, and robust support for modern web technologies.
npm install esbuild-sunos-64Verified import paths — ran on the pinned version, not inferred.
Demonstrates a basic esbuild setup to bundle a TypeScript file into a single JavaScript output, including minification, sourcemaps, and targeting a browser environment. This script also creates and cleans up temporary input files for a self-contained example.
Update your `package.json` to pin the exact esbuild version or use a `~` semver range. Always review the changelog for specific breaking changes when upgrading, particularly across minor versions.
To bundle node_modules dependencies, explicitly remove them from the `external` option. For Node.js targets, `external: ['*']` is often appropriate to prevent bundling all external packages and relying on Node.js's module resolution.
Configure appropriate loaders in your esbuild build options. For example, `{ loader: { '.css': 'css', '.png': 'file' } }` for CSS and image files, or use plugins designed to handle specific asset types.Migrate away from `startService`. Directly call `build` or `transform` functions. If you need to customize the esbuild binary path, use the `ESBUILD_BINARY_PATH` environment variable or the `esbuild.config` option in some frameworks.
Upgrade esbuild to version 0.25.0 or later immediately. If using esbuild indirectly (e.g., via Angular), utilize package `overrides` or `resolutions` to enforce the secure version. Always verify the fix with `npm audit`.
Add a `loader` configuration to your build options for the problematic file type, e.g., `{ loader: { '.css': 'css', '.png': 'file' } }` for CSS files, or `'file'` for assets.Ensure the module is installed. If it's a `node_modules` dependency, either explicitly include it in your bundle by removing it from the `external` option or, for Node.js targets, ensure it's correctly externalized (`external: ['*']`). Verify the import path is correct and consider `platform: 'node'` if bundling for Node.js.
Adjust your `target` option in esbuild to a newer ECMAScript version (e.g., `es2020`, `esnext`, `es2023`). Review the specified file and line number to correct any syntax mistakes.
When bundling for Node.js (`platform: 'node'`), prioritize `format: 'cjs'` or carefully manage external ESM dependencies. If `format: 'esm'` is used, CJS dependencies might need to be explicitly bundled or dynamic `import()` used instead of `require()`. Review esbuild's `--format` and `--packages` options in conjunction with your dependencies.
No dependency data recorded yet.