Security News
Introducing the Socket Python SDK
The initial version of the Socket Python SDK is now on PyPI, enabling developers to more easily interact with the Socket REST API in Python projects.
@esbuild/win32-ia32
Advanced tools
The Windows 32-bit binary for esbuild, a JavaScript bundler.
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.
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))
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 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 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 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.
This is the Windows 32-bit binary for esbuild, a JavaScript bundler and minifier. See https://github.com/evanw/esbuild for details.
0.23.1
Allow using the node:
import prefix with es*
targets (#3821)
The node:
prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs"
can also be written import fs from "node:fs"
. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14
so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022
removes the node:
prefix because none of the es*
targets are known to support this feature. This release adds the support for the node:
flag to esbuild's internal compatibility table for es*
to allow you to use compound targets like this:
// Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
Fix a panic when using the CLI with invalid build flags if --analyze
is present (#3834)
Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze
flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze
is implemented) to a null build object. The panic has been fixed in this release.
Fix incorrect location of certain error messages (#3845)
This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.
Print comments before case clauses in switch statements (#3838)
With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).
Fix a memory leak with pluginData
(#3825)
With this release, the build context's internal pluginData
cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData
objects from onResolve
and/or onLoad
callbacks.
FAQs
The Windows 32-bit binary for esbuild, a JavaScript bundler.
The npm package @esbuild/win32-ia32 receives a total of 4,502,221 weekly downloads. As such, @esbuild/win32-ia32 popularity was classified as popular.
We found that @esbuild/win32-ia32 demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The initial version of the Socket Python SDK is now on PyPI, enabling developers to more easily interact with the Socket REST API in Python projects.
Security News
Floating dependency ranges in npm can introduce instability and security risks into your project by allowing unverified or incompatible versions to be installed automatically, leading to unpredictable behavior and potential conflicts.
Security News
A new Rust RFC proposes "Trusted Publishing" for Crates.io, introducing short-lived access tokens via OIDC to improve security and reduce risks associated with long-lived API tokens.