@esbuild/linux-arm64

What is @esbuild/linux-arm64?

The @esbuild/linux-arm64 npm package is a binary package for the esbuild bundler and minifier tool. It is specifically compiled for Linux systems running on ARM64 architecture. Esbuild is a fast JavaScript bundler and minifier that compiles TypeScript, JavaScript, and JSX files into a single file for use in web applications.

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

Bundling JavaScript files

This code sample demonstrates how to bundle multiple JavaScript files into a single file using esbuild.

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

Minifying JavaScript

This code sample shows how to minify a JavaScript file, reducing its size for production deployment.

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

Transpiling TypeScript

This code sample illustrates how to transpile TypeScript files into JavaScript using esbuild.

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

Transforming JSX

This code sample demonstrates how to transform JSX syntax into JavaScript, which is useful for React applications.

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

Other packages similar to @esbuild/linux-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 more complex features and plugin system.

rollup

Rollup is another module bundler that is well-suited for creating libraries and applications. It focuses on producing smaller bundles through tree-shaking, but it is not as fast as esbuild.

parcel

Parcel is a web application bundler that offers a zero-configuration setup. It is known for its ease of use and fast build times, but esbuild typically outperforms it in terms of speed.

terser

Terser is a JavaScript parser, mangler, and compressor toolkit for ES6+. It is commonly used for minifying JavaScript code, similar to esbuild's minification feature, but does not bundle files.

README

esbuild

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