@esbuild/darwin-arm64

What is @esbuild/darwin-arm64?

The @esbuild/darwin-arm64 npm package is a binary package for the esbuild bundler and minifier. It is specifically compiled for macOS on ARM64 architecture (Apple Silicon). Esbuild is a fast JavaScript bundler and minifier that compiles TypeScript, JavaScript, and JSX files into a single output file. It is designed to be extremely fast and efficient, taking advantage of parallelism and native code execution.

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

Bundling JavaScript

This feature allows you to bundle multiple JavaScript files into a single output file, which can be used in a browser or other JavaScript environment.

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

Minifying JavaScript

This feature enables the minification of JavaScript code to reduce file size and improve load times in production environments.

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

Transpiling TypeScript

This feature allows you to transpile TypeScript code into JavaScript, enabling you to use TypeScript's advanced features while maintaining compatibility with JavaScript environments.

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

JSX Support

This feature provides support for JSX syntax, commonly used in React applications, allowing you to bundle and transpile JSX files directly.

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

Other packages similar to @esbuild/darwin-arm64

webpack

Webpack is a popular JavaScript module bundler with a large ecosystem of plugins. It is more configurable than esbuild but generally slower due to its JavaScript-based architecture as opposed to the Go-based architecture of esbuild.

rollup

Rollup is another JavaScript module bundler that focuses on producing efficient bundles for modern module formats like ES modules. It is known for its tree-shaking capabilities but is not as fast as esbuild.

parcel

Parcel is a web application bundler that offers a zero-configuration experience. It is user-friendly and supports a wide range of file types out of the box, but it does not match the speed of esbuild.

terser

Terser is a JavaScript parser, mangler, and compressor toolkit for ES6+. It is commonly used for minifying JavaScript code. While it is efficient at reducing code size, it does not offer bundling capabilities and is slower than esbuild.

README

esbuild

This is the macOS ARM 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.