@esbuild/win32-ia32

What is @esbuild/win32-ia32?

The @esbuild/win32-ia32 npm package is a binary distribution of esbuild for Windows (32-bit) systems. Esbuild is an extremely fast JavaScript bundler and minifier. It compiles TypeScript and JavaScript into code that can run in the browser, and it can bundle many files into a single output file. It's designed to be very fast and efficient.

What are @esbuild/win32-ia32's main functionalities?

Bundling JavaScript

This feature allows you to bundle multiple JavaScript files into a single file, which can be useful for reducing the number of HTTP requests needed to load a web page.

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, which reduces file size by removing unnecessary characters without changing its functionality.

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, making it possible to use TypeScript's features while still targeting environments that only support JavaScript.

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

Other packages similar to @esbuild/win32-ia32

webpack

Webpack is a powerful module bundler that can transform front-end assets like HTML, CSS, and JavaScript. It's more configurable than esbuild but generally slower due to its complexity and feature-rich nature.

parcel

Parcel is a web application bundler that offers a zero-configuration experience. It's known for its simplicity and speed, but esbuild typically outperforms it in terms of build times.

rollup

Rollup is another module bundler for JavaScript which is best known for its tree-shaking capabilities, allowing for the creation of smaller bundles. It's more focused on bundling for libraries and has a different scope compared to esbuild's focus on speed.

terser

Terser is a JavaScript parser, mangler and compressor toolkit for ES6+. It's specifically focused on minification and is often used in conjunction with other bundling tools rather than as a standalone bundler like esbuild.

README

esbuild

This is the Windows 32-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.