-
Notifications
You must be signed in to change notification settings - Fork 36
Commit 59ef7a3
authored
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4&size=40){kind=avatar}
chore(deps): update dependency esbuild to v0.24.2 (#1123)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [esbuild](https://redirect.github.com/evanw/esbuild) | [`0.24.0` ->
`0.24.2`](https://renovatebot.com/diffs/npm/esbuild/0.24.0/0.24.2) |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
---
### Release Notes
<details>
<summary>evanw/esbuild (esbuild)</summary>
###
[`v0.24.2`](https://redirect.github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0242)
[Compare
Source](https://redirect.github.com/evanw/esbuild/compare/v0.24.1...v0.24.2)
- Fix regression with `--define` and `import.meta`
([#​4010](https://redirect.github.com/evanw/esbuild/issues/4010),
[#​4012](https://redirect.github.com/evanw/esbuild/issues/4012),
[#​4013](https://redirect.github.com/evanw/esbuild/pull/4013))
The previous change in version 0.24.1 to use a more expression-like
parser for `define` values to allow quoted property names introduced a
regression that removed the ability to use `--define:import.meta=...`.
Even though `import` is normally a keyword that can't be used as an
identifier, ES modules special-case the `import.meta` expression to
behave like an identifier anyway. This change fixes the regression.
This fix was contributed by
[@​sapphi-red](https://redirect.github.com/sapphi-red).
###
[`v0.24.1`](https://redirect.github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0241)
[Compare
Source](https://redirect.github.com/evanw/esbuild/compare/v0.24.0...v0.24.1)
- Allow `es2024` as a target in `tsconfig.json`
([#​4004](https://redirect.github.com/evanw/esbuild/issues/4004))
TypeScript recently [added
`es2024`](https://devblogs.microsoft.com/typescript/announcing-typescript-5-7/#support-for---target-es2024-and---lib-es2024)
as a compilation target, so esbuild now supports this in the `target`
field of `tsconfig.json` files, such as in the following configuration
file:
```json
{
"compilerOptions": {
"target": "ES2024"
}
}
```
As a reminder, the only thing that esbuild uses this field for is
determining whether or not to use legacy TypeScript behavior for class
fields. You can read more in [the
documentation](https://esbuild.github.io/content-types/#tsconfig-json).
This fix was contributed by
[@​billyjanitsch](https://redirect.github.com/billyjanitsch).
- Allow automatic semicolon insertion after `get`/`set`
This change fixes a grammar bug in the parser that incorrectly treated
the following code as a syntax error:
```ts
class Foo {
get
*x() {}
set
*y() {}
}
```
The above code will be considered valid starting with this release. This
change to esbuild follows a [similar change to
TypeScript](https://redirect.github.com/microsoft/TypeScript/pull/60225)
which will allow this syntax starting with TypeScript 5.7.
- Allow quoted property names in `--define` and `--pure`
([#​4008](https://redirect.github.com/evanw/esbuild/issues/4008))
The `define` and `pure` API options now accept identifier expressions
containing quoted property names. Previously all identifiers in the
identifier expression had to be bare identifiers. This change now makes
`--define` and `--pure` consistent with `--global-name`, which already
supported quoted property names. For example, the following is now
possible:
```js
// The following code now transforms to "return true;\n"
console.log(esbuild.transformSync(
`return process.env['SOME-TEST-VAR']`,
{ define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
))
```
Note that if you're passing values like this on the command line using
esbuild's `--define` flag, then you'll need to know how to escape quote
characters for your shell. You may find esbuild's JavaScript API more
ergonomic and portable than writing shell code.
- Minify empty `try`/`catch`/`finally` blocks
([#​4003](https://redirect.github.com/evanw/esbuild/issues/4003))
With this release, esbuild will now attempt to minify empty `try`
blocks:
```js
// Original code
try {} catch { foo() } finally { bar() }
// Old output (with --minify)
try{}catch{foo()}finally{bar()}
// New output (with --minify)
bar();
```
This can sometimes expose additional minification opportunities.
- Include `entryPoint` metadata for the `copy` loader
([#​3985](https://redirect.github.com/evanw/esbuild/issues/3985))
Almost all entry points already include a `entryPoint` field in the
`outputs` map in esbuild's build metadata. However, this wasn't the case
for the `copy` loader as that loader is a special-case that doesn't
behave like other loaders. This release adds the `entryPoint` field in
this case.
- Source mappings may now contain `null` entries
([#​3310](https://redirect.github.com/evanw/esbuild/issues/3310),
[#​3878](https://redirect.github.com/evanw/esbuild/issues/3878))
With this change, sources that result in an empty source map may now
emit a `null` source mapping (i.e. one with a generated position but
without a source index or original position). This change improves
source map accuracy by fixing a problem where minified code from a
source without any source mappings could potentially still be associated
with a mapping from another source file earlier in the generated output
on the same minified line. It manifests as nonsensical files in source
mapped stack traces. Now the `null` mapping "resets" the source map so
that any lookups into the minified code without any mappings resolves to
`null` (which appears as the output file in stack traces) instead of the
incorrect source file.
This change shouldn't affect anything in most situations. I'm only
mentioning it in the release notes in case it introduces a bug with
source mapping. It's part of a work-in-progress future feature that will
let you omit certain unimportant files from the generated source map to
reduce source map size.
- Avoid using the parent directory name for determinism
([#​3998](https://redirect.github.com/evanw/esbuild/issues/3998))
To make generated code more readable, esbuild includes the name of the
source file when generating certain variable names within the file.
Specifically bundling a CommonJS file generates a variable to store the
lazily-evaluated module initializer. However, if a file is named
`index.js` (or with a different extension), esbuild will use the name of
the parent directory instead for a better name (since many packages have
files all named `index.js` but have unique directory names).
This is problematic when the bundle entry point is named `index.js` and
the parent directory name is non-deterministic (e.g. a temporary
directory created by a build script). To avoid non-determinism in
esbuild's output, esbuild will now use `index` instead of the parent
directory in this case. Specifically this will happen if the parent
directory is equal to esbuild's `outbase` API option, which defaults to
the [lowest common
ancestor](https://en.wikipedia.org/wiki/Lowest_common_ancestor) of all
user-specified entry point paths.
- Experimental support for esbuild on NetBSD
([#​3974](https://redirect.github.com/evanw/esbuild/pull/3974))
With this release, esbuild now has a published binary executable for
[NetBSD](https://www.netbsd.org/) in the
[`@esbuild/netbsd-arm64`](https://www.npmjs.com/package/@​esbuild/netbsd-arm64)
npm package, and esbuild's installer has been modified to attempt to use
it when on NetBSD. Hopefully this makes installing esbuild via npm work
on NetBSD. This change was contributed by
[@​bsiegert](https://redirect.github.com/bsiegert).
1 parent 952c43f commit 59ef7a3Copy full SHA for 59ef7a3
1 file changed
+590
-99
lines changed
0 commit comments