@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.20.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.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

• Work around API deprecations in Deno 1.40.x (#3609, #3611)

  Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

  Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

• Reorder implicit file extensions within node_modules (#3341, #3608)

  In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

  With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

  Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.