Security News
The Unpaid Backbone of Open Source: Solo Maintainers Face Increasing Security Demands
Solo open source maintainers face burnout and security challenges, with 60% unpaid and 60% considering quitting.
@esbuild/win32-ia32
Advanced tools
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.21.5
Fix Symbol.metadata
on classes without a class decorator (#3781)
This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata
property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata
property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.
Allow unknown import attributes to be used with the copy
loader (#3792)
Import attributes (the with
keyword on import
statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js
as type bagel
:
// This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }
Because of that, bundling this code with esbuild is an error unless the file ./bagel.js
is external to the bundle (such as with --bundle --external:./bagel.js
).
However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy
loader. That's because the copy
loader behaves similarly to --external
in that the file is left external to the bundle. The difference is that the copy
loader copies the file into the output folder and rewrites the import path while --external
doesn't. That means the following will now work with the copy
loader (such as with --bundle --loader:.bagel=copy
):
// This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }
Support import attributes with glob-style imports (#3797)
This release adds support for import attributes (the with
option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:
async function loadLocale(locale: string): Locale {
const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
return unpackLocale(locale, data)
}
Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:
✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
example.ts:2:28:
2 │ const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~
In addition, this change means plugins can now access the contents of with
for glob-style imports.
Support ${configDir}
in tsconfig.json
files (#3782)
This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir}
is now respected at the start of baseUrl
and paths
values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json
files specified via extends
refer to the directory of the top-level tsconfig.json
file. Here is an example:
{
"compilerOptions": {
"paths": {
"js/*": ["${configDir}/dist/js/*"]
}
}
}
You can read more in TypeScript's blog post about their upcoming 5.5 release. Note that this feature does not make use of template literals (you need to use "${configDir}/dist/js/*"
not `${configDir}/dist/js/*`
). The syntax for tsconfig.json
is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes ${configDir}
in strings for certain path-like properties, and only at the beginning of the string.
Fix internal error with --supported:object-accessors=false
(#3794)
This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with --supported:object-accessors=false
. The reason is that esbuild introduced code that does { get [name]() {} }
which uses both the object-extensions
feature for the [name]
and the object-accessors
feature for the get
, but esbuild was incorrectly only checking for object-extensions
and not for object-accessors
. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add --supported:object-extensions=false
.
FAQs
The Windows 32-bit binary for esbuild, a JavaScript bundler.
The npm package @esbuild/win32-ia32 receives a total of 3,564,220 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
Solo open source maintainers face burnout and security challenges, with 60% unpaid and 60% considering quitting.
Security News
License exceptions modify the terms of open source licenses, impacting how software can be used, modified, and distributed. Developers should be aware of the legal implications of these exceptions.
Security News
A developer is accusing Tencent of violating the GPL by modifying a Python utility and changing its license to BSD, highlighting the importance of copyleft compliance.