@esbuild/darwin-x64

What is @esbuild/darwin-x64?

The @esbuild/darwin-x64 npm package is a binary package for the esbuild bundler optimized for macOS on x64 architectures. Esbuild is a fast JavaScript bundler and minifier. It compiles TypeScript and JavaScript into efficient code that can be executed in the browser or on Node.js. This package specifically contains the esbuild binary for macOS (Darwin) systems with x64 architecture, facilitating web development tasks such as bundling, minification, and transpilation.

What are @esbuild/darwin-x64's main functionalities?

JavaScript and TypeScript Bundling

This feature allows you to bundle multiple JavaScript or TypeScript files into a single file. The code sample demonstrates how to bundle an entry file named 'app.js' into an output file named 'out.js'.

require('esbuild').build({
  entryPoints: ['app.js'],
  bundle: true,
  outfile: 'out.js'
}).catch(() => process.exit(1))

Minification

This feature enables the minification of JavaScript files to reduce their size by removing unnecessary characters without changing their functionality. The code sample shows how to minify an entry file 'app.js' into a minified output file 'out.min.js'.

require('esbuild').build({
  entryPoints: ['app.js'],
  minify: true,
  outfile: 'out.min.js'
}).catch(() => process.exit(1))

Transpilation

This feature allows for the transpilation of TypeScript code into JavaScript, making it compatible with older browsers or environments that do not support TypeScript natively. The code sample demonstrates bundling and transpiling a TypeScript file 'app.ts' into a JavaScript file 'out.js'.

require('esbuild').build({
  entryPoints: ['app.ts'],
  bundle: true,
  outfile: 'out.js',
  loader: { '.ts': 'ts' }
}).catch(() => process.exit(1))

Other packages similar to @esbuild/darwin-x64

webpack

Webpack is a powerful module bundler for JavaScript applications. It offers a wide range of plugins and loaders to transform, bundle, or package almost any resource or asset. Compared to @esbuild/darwin-x64, webpack is more feature-rich and configurable but generally slower in terms of build speed.

rollup

Rollup is another JavaScript module bundler that focuses on producing efficient bundles for modern module formats like ES6. It's known for its simplicity and efficiency, especially for library authors. Rollup is similar to @esbuild/darwin-x64 in terms of speed and efficiency but lacks some of the more advanced optimization features found in esbuild.

parcel

Parcel is a web application bundler that offers out-of-the-box support for many web development languages and tools without the need for configuration. It's designed to be fast, utilizing multicore processing for efficient builds. Compared to @esbuild/darwin-x64, Parcel provides a more integrated development experience with less focus on manual configuration.

README

esbuild

This is the macOS 64-bit binary for esbuild, a JavaScript bundler and minifier. See https://github.com/evanw/esbuild for details.

Changelog

0.24.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

• Drop support for older platforms (#3902)

  This release drops support for the following operating system:

  • macOS 10.15 Catalina

  This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

  Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

  git clone https://github.com/evanw/esbuild.git
  cd esbuild
  go build ./cmd/esbuild
  ./esbuild --version
  

• Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

  Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

• Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

  TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

• Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

  Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

• Work around more issues with Deno 1.31+ (#3917)

  This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

  This fix was contributed by @Joshix-1.