Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

await using normative changes #58624

Merged
merged 2 commits into from
May 29, 2024
Merged

await using normative changes #58624

merged 2 commits into from
May 29, 2024

Conversation

rbuckton
Copy link
Member

@rbuckton rbuckton commented May 22, 2024

This aligns TypeScript with a number of normative updates to the Explicit Resource Management proposal, per #58622:

  • [Symbol.dispose]() methods are wrapped in a closure when used in an await using declaration.
  • Promise-like values returned by [Symbol.dispose]() are ignored in an await using declaration.
  • Synchronous exceptions thrown by [Symbol.dispose]() in an await using declaration are turned into rejections.

See microsoft/tslib#258 for the companion PR for tslib.

Fixes #58077
Fixes #58622

@rbuckton rbuckton changed the title 'await using' normative changes await using normative changes May 24, 2024
@rbuckton rbuckton merged commit 2a9e4b8 into main May 29, 2024
28 checks passed
@rbuckton rbuckton deleted the fix58077 branch May 29, 2024 21:34
@rbuckton
Copy link
Member Author

@sandersn if you can take a look at microsoft/tslib#258 too, I'd appreciate it.

skeate added a commit to skeate/TypeScript that referenced this pull request Jun 1, 2024
* upstream/main: (37 commits)
  Added NoTruncation flag to completions (microsoft#58719)
  Clone node to remove location even when it has been modified if needed (microsoft#58706)
  Properly account for `this` argument in intersection apparent type caching (microsoft#58677)
  Fix: Include Values of Script Extensions for Unicode Property Value Expressions in Regular Expressions (microsoft#58615)
  In `reScanSlashToken` use `charCodeChecked` not `codePointChecked` (microsoft#58727)
  Shorten error spans for errors reported on constructor declarations (microsoft#58061)
  Mark file as skips typechecking if it contains ts-nocheck (microsoft#58593)
  Fixed an issue with broken `await using` declarations in `for of` loops (microsoft#56466)
  Do not expand type references in keyof and index access (microsoft#58715)
  Improve the performance of isolatedDeclarations quickfix  (microsoft#58722)
  Unwrap `NoInfer` types when narrowing (microsoft#58292)
  Recover from type reuse errors by falling back to inferred type printing (microsoft#58720)
  Fixing self import (microsoft#58718)
  Enable JS emit for noCheck and noCheck for transpileModule (microsoft#58364)
  Revert PR 55371 (microsoft#58702)
  Update dependencies (microsoft#58639)
  Fix baselines after PR 58621 (microsoft#58705)
  Do not infer `yield*` type from contextual `TReturn` (microsoft#58621)
  `await using` normative changes (microsoft#58624)
  Handling statements from a known source file (microsoft#58679)
  ...
renovate bot added a commit to ayushmanchhabra/vsx that referenced this pull request Jul 1, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [esbuild](https://github.com/evanw/esbuild) | [`~0.21.5` ->
`~0.22.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.5/0.22.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.5/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.5/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/ayushmanchhabra/vsx).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
github-merge-queue bot pushed a commit to rolldown/rolldown that referenced this pull request Jul 1, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@codemirror/view](https://github.com/codemirror/view) | [`6.28.1`
->
`6.28.2`](https://renovatebot.com/diffs/npm/@codemirror%2fview/6.28.1/6.28.2)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/@codemirror%2fview/6.28.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@codemirror%2fview/6.28.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@codemirror%2fview/6.28.1/6.28.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@codemirror%2fview/6.28.1/6.28.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
|
[@types/lodash](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/lodash)
([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/lodash))
| [`4.17.5` ->
`4.17.6`](https://renovatebot.com/diffs/npm/@types%2flodash/4.17.5/4.17.6)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2flodash/4.17.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@types%2flodash/4.17.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@types%2flodash/4.17.5/4.17.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2flodash/4.17.5/4.17.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
|
[@types/mocha](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/mocha)
([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/mocha))
| [`10.0.6` ->
`10.0.7`](https://renovatebot.com/diffs/npm/@types%2fmocha/10.0.6/10.0.7)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2fmocha/10.0.7?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@types%2fmocha/10.0.7?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@types%2fmocha/10.0.6/10.0.7?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2fmocha/10.0.6/10.0.7?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
|
[@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node)
([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node))
| [`20.14.2` ->
`20.14.9`](https://renovatebot.com/diffs/npm/@types%2fnode/20.14.2/20.14.9)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2fnode/20.14.9?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@types%2fnode/20.14.9?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@types%2fnode/20.14.2/20.14.9?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2fnode/20.14.2/20.14.9?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [cspell](https://streetsidesoftware.github.io/cspell/)
([source](https://github.com/streetsidesoftware/cspell/tree/HEAD/packages/cspell))
| [`8.8.4` ->
`8.9.1`](https://renovatebot.com/diffs/npm/cspell/8.8.4/8.9.1) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/cspell/8.9.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/cspell/8.9.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/cspell/8.8.4/8.9.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/cspell/8.8.4/8.9.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [esbuild](https://github.com/evanw/esbuild) | [`^0.21.5` ->
`^0.22.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.5/0.22.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.5/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.5/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [execa](https://github.com/sindresorhus/execa) | [`9.2.0` ->
`9.3.0`](https://renovatebot.com/diffs/npm/execa/9.2.0/9.3.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/execa/9.3.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/execa/9.3.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/execa/9.2.0/9.3.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/execa/9.2.0/9.3.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [glob](https://github.com/isaacs/node-glob) | [`10.4.1` ->
`10.4.2`](https://renovatebot.com/diffs/npm/glob/10.4.1/10.4.2) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/glob/10.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/glob/10.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/glob/10.4.1/10.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/glob/10.4.1/10.4.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [mocha](https://mochajs.org/)
([source](https://github.com/mochajs/mocha)) | [`10.4.0` ->
`10.5.2`](https://renovatebot.com/diffs/npm/mocha/10.4.0/10.5.2) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/mocha/10.5.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/mocha/10.5.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/mocha/10.4.0/10.5.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/mocha/10.4.0/10.5.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [npm-rolldown](https://rolldown.rs/)
([source](https://github.com/rolldown/rolldown/tree/HEAD/packages/rolldown))
| [`0.10.4-snapshot-66e8482-20240616163535` ->
`0.10.5`](https://renovatebot.com/diffs/npm/npm-rolldown/0.10.4-snapshot-66e8482-20240616163535/0.10.5)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/npm-rolldown/0.10.5?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/npm-rolldown/0.10.5?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/npm-rolldown/0.10.4-snapshot-66e8482-20240616163535/0.10.5?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/npm-rolldown/0.10.4-snapshot-66e8482-20240616163535/0.10.5?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [oxlint](https://oxc.rs)
([source](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxlint)) |
[`0.4.4` ->
`0.5.1`](https://renovatebot.com/diffs/npm/oxlint/0.4.4/0.5.1) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/oxlint/0.5.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/oxlint/0.5.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/oxlint/0.4.4/0.5.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/oxlint/0.4.4/0.5.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [pnpm](https://pnpm.io) ([source](https://github.com/pnpm/pnpm)) |
[`9.3.0` -> `9.4.0`](https://renovatebot.com/diffs/npm/pnpm/9.3.0/9.4.0)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/pnpm/9.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/pnpm/9.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/pnpm/9.3.0/9.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/pnpm/9.3.0/9.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [typescript](https://www.typescriptlang.org/)
([source](https://github.com/Microsoft/TypeScript)) | [`5.4.5` ->
`5.5.2`](https://renovatebot.com/diffs/npm/typescript/5.4.5/5.5.2) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/typescript/5.5.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/typescript/5.5.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/typescript/5.4.5/5.5.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/typescript/5.4.5/5.5.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [vite](https://vitejs.dev)
([source](https://github.com/vitejs/vite/tree/HEAD/packages/vite)) |
[`5.3.1` -> `5.3.2`](https://renovatebot.com/diffs/npm/vite/5.3.1/5.3.2)
|
[![age](https://developer.mend.io/api/mc/badges/age/npm/vite/5.3.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/vite/5.3.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/vite/5.3.1/5.3.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vite/5.3.1/5.3.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [vue](https://github.com/vuejs/core/tree/main/packages/vue#readme)
([source](https://github.com/vuejs/core)) | [`3.4.29` ->
`3.4.31`](https://renovatebot.com/diffs/npm/vue/3.4.29/3.4.31) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/vue/3.4.31?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/vue/3.4.31?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/vue/3.4.29/3.4.31?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vue/3.4.29/3.4.31?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [vue-router](https://github.com/vuejs/router) | [`4.3.3` ->
`4.4.0`](https://renovatebot.com/diffs/npm/vue-router/4.3.3/4.4.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/vue-router/4.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/vue-router/4.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/vue-router/4.3.3/4.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vue-router/4.3.3/4.4.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [zx](https://github.com/google/zx) | [`8.1.2` ->
`8.1.3`](https://renovatebot.com/diffs/npm/zx/8.1.2/8.1.3) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/zx/8.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/zx/8.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/zx/8.1.2/8.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/zx/8.1.2/8.1.3?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>codemirror/view (@&#8203;codemirror/view)</summary>

###
[`v6.28.2`](https://github.com/codemirror/view/blob/HEAD/CHANGELOG.md#6282-2024-06-21)

[Compare
Source](https://github.com/codemirror/view/compare/6.28.1...6.28.2)

##### Bug fixes

Only use `EditContext` on Chrome versions that support passing it an
inverted selection range.

Fix an issue that prevented non-inclusive block widgets from having
their `updateDOM` method called when changed.

Re-enable `EditContext` use on Chrome 126 and up.

</details>

<details>
<summary>streetsidesoftware/cspell (cspell)</summary>

###
[`v8.9.1`](https://github.com/streetsidesoftware/cspell/blob/HEAD/packages/cspell/CHANGELOG.md#small891-2024-06-20-small)

[Compare
Source](https://github.com/streetsidesoftware/cspell/compare/v8.9.0...v8.9.1)

- docs: format tables in generated docs
([#&#8203;5776](https://github.com/streetsidesoftware/cspell/issues/5776))
([02e0359](https://github.com/streetsidesoftware/cspell/commit/02e0359)),
closes
[#&#8203;5776](https://github.com/streetsidesoftware/cspell/issues/5776)

###
[`v8.9.0`](https://github.com/streetsidesoftware/cspell/blob/HEAD/packages/cspell/CHANGELOG.md#890-2024-06-18)

[Compare
Source](https://github.com/streetsidesoftware/cspell/compare/v8.8.4...v8.9.0)

**Note:** Version bump only for package cspell

</details>

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

</details>

<details>
<summary>sindresorhus/execa (execa)</summary>

###
[`v9.3.0`](https://github.com/sindresorhus/execa/releases/tag/v9.3.0)

[Compare
Source](https://github.com/sindresorhus/execa/compare/v9.2.0...v9.3.0)

#### Features

- The [`verbose`](docs/api.md#optionsverbose) option can now be [a
function](docs/api.md#verbose-function) to [customize
logging](docs/debugging.md#custom-logging).
([#&#8203;1130](https://github.com/sindresorhus/execa/issues/1130))

</details>

<details>
<summary>isaacs/node-glob (glob)</summary>

###
[`v10.4.2`](https://github.com/isaacs/node-glob/compare/v10.4.1...eef7ea35afe511079c5bf83862ed57ece2bbf7fa)

[Compare
Source](https://github.com/isaacs/node-glob/compare/v10.4.1...v10.4.2)

</details>

<details>
<summary>mochajs/mocha (mocha)</summary>

###
[`v10.5.2`](https://github.com/mochajs/mocha/blob/HEAD/CHANGELOG.md#1052--2024-05-25)

[Compare
Source](https://github.com/mochajs/mocha/compare/v10.5.1...v10.5.2)

##### :bug: Fixes

- [#&#8203;5032](https://github.com/mochajs/mocha/pull/5032) fix:
better tracking of seen objects in error serialization
([**@&#8203;sam-super**](https://github.com/sam-super))

###
[`v10.5.1`](https://github.com/mochajs/mocha/blob/HEAD/CHANGELOG.md#1051--2024-05-24)

[Compare
Source](https://github.com/mochajs/mocha/compare/v10.5.0...v10.5.1)

##### :bug: Fixes

- [#&#8203;5086](https://github.com/mochajs/mocha/pull/5086) fix: Add
error handling for nonexistent file case with --file option
([**@&#8203;khoaHyh**](https://github.com/khoaHyh))

###
[`v10.5.0`](https://github.com/mochajs/mocha/blob/HEAD/CHANGELOG.md#1050--2024-05-24)

[Compare
Source](https://github.com/mochajs/mocha/compare/v10.4.0...v10.5.0)

##### :tada: Enhancements

- [#&#8203;5015](https://github.com/mochajs/mocha/pull/5015) feat: use
\<progress> and \<svg> for browser progress indicator instead of
\<canvas> ([**@&#8203;yourWaifu**](https://github.com/yourWaifu))
- [#&#8203;5143](https://github.com/mochajs/mocha/pull/5143) feat:
allow using any 3.x chokidar dependencies
([**@&#8203;simhnna**](https://github.com/simhnna))
- [#&#8203;4835](https://github.com/mochajs/mocha/pull/4835) feat: add
MOCHA_OPTIONS env variable
([**@&#8203;icholy**](https://github.com/icholy))

##### :bug: Fixes

- [#&#8203;5107](https://github.com/mochajs/mocha/pull/5107) fix:
include stack in browser uncaught error reporting
([**@&#8203;JoshuaKGoldberg**](https://github.com/JoshuaKGoldberg))

##### :nut_and_bolt: Other

- [#&#8203;5110](https://github.com/mochajs/mocha/pull/5110) chore:
switch two-column list styles to be opt-in
([**@&#8203;marjys**](https://github.com/marjys))
- [#&#8203;5135](https://github.com/mochajs/mocha/pull/5135) chore:
fix some typos in comments
([**@&#8203;StevenMia**](https://github.com/StevenMia))
- [#&#8203;5130](https://github.com/mochajs/mocha/pull/5130) chore:
rename 'master' to 'main' in docs and tooling
([**@&#8203;JoshuaKGoldberg**](https://github.com/JoshuaKGoldberg))

</details>

<details>
<summary>rolldown/rolldown (npm-rolldown)</summary>

###
[`v0.10.5`](https://github.com/rolldown/rolldown/blob/HEAD/CHANGELOG.md#0105-2024-06-27)

[Compare
Source](https://github.com/rolldown/rolldown/compare/v0.10.4...v0.10.5)

##### Bug Fixes

- `forbid_const_assign_when_lowering_using` test
([#&#8203;1413](https://github.com/rolldown/rolldown/issues/1413))
([0d15f0e](https://github.com/rolldown/rolldown/commit/0d15f0e6d55192b1ac763e069b7b01f508a8c776))
- **cjs:** handle `export * from 'external'` correctly
([#&#8203;1363](https://github.com/rolldown/rolldown/issues/1363))
([9dbb803](https://github.com/rolldown/rolldown/commit/9dbb80346b075d36b2be379cf86ed6652dd7470f))
- **cjs:** should not panic if wrapped esm module `export * from
'external'`
([#&#8203;1450](https://github.com/rolldown/rolldown/issues/1450))
([c62a512](https://github.com/rolldown/rolldown/commit/c62a51255e4ea0689300b14310b5c50655675fa2))
- **core:** don't panic on require calls that are invalid to bundler
([#&#8203;1445](https://github.com/rolldown/rolldown/issues/1445))
([5fb31d0](https://github.com/rolldown/rolldown/commit/5fb31d0d254128825df9441b23da58e3f6663060))
- **deps:** update dependency
[@&#8203;codemirror/view](https://github.com/codemirror/view) to
v6.27.0
([#&#8203;1347](https://github.com/rolldown/rolldown/issues/1347))
([c6e1937](https://github.com/rolldown/rolldown/commit/c6e1937f867f40a58c740ee4b3e472076bf4a79f))
- **deps:** update dependency
[@&#8203;rollup/plugin-commonjs](https://github.com/rollup/plugin-commonjs)
to v26
([#&#8203;1353](https://github.com/rolldown/rolldown/issues/1353))
([7dbbfbc](https://github.com/rolldown/rolldown/commit/7dbbfbc2dd53c9583742957dc9a00dd7c8080961))
- **docs:** update requirement of node version in contribution guide
([#&#8203;1345](https://github.com/rolldown/rolldown/issues/1345))
([0d979b6](https://github.com/rolldown/rolldown/commit/0d979b60ec2f0ef6977031f030942cf387c76bda))
- export some typing
([#&#8203;1405](https://github.com/rolldown/rolldown/issues/1405))
([c42f7b3](https://github.com/rolldown/rolldown/commit/c42f7b373c3d8b85d7dd4f1549605ff99a1426ae))
- option hook can be async and can return overwritten input options
([#&#8203;1422](https://github.com/rolldown/rolldown/issues/1422))
([38a2c3e](https://github.com/rolldown/rolldown/commit/38a2c3e6a9d782efdea45a71d15cae589647ea37))
- outputOptions hook argument should be OutputOptions
([#&#8203;1430](https://github.com/rolldown/rolldown/issues/1430))
([472848b](https://github.com/rolldown/rolldown/commit/472848b56288ae5fa59db792cff83cf379885323))
- **resolver:** ensure we always pass an absolute path to oxc_resolver
([#&#8203;1442](https://github.com/rolldown/rolldown/issues/1442))
([3ffe43f](https://github.com/rolldown/rolldown/commit/3ffe43f62ecdfb36976daf5870958b9d002ee0be))
- rolldown typing
([#&#8203;1387](https://github.com/rolldown/rolldown/issues/1387))
([440e68e](https://github.com/rolldown/rolldown/commit/440e68ed7bb06c972cda3b12874d748ec8ef366d))
- **rolldown_fs:** canonicalize polyfill on wasi platform
([#&#8203;1436](https://github.com/rolldown/rolldown/issues/1436))
([2530866](https://github.com/rolldown/rolldown/commit/2530866317f07426a749d960979984f1fa12d198))

##### Features

- add assetFileNames binding
([#&#8203;1360](https://github.com/rolldown/rolldown/issues/1360))
([c86f784](https://github.com/rolldown/rolldown/commit/c86f78406546f20db34d606980810c51bcb86fcc))
- advanced barrel exports optimization.
([#&#8203;1374](https://github.com/rolldown/rolldown/issues/1374))
([33a6db5](https://github.com/rolldown/rolldown/commit/33a6db5cf3a33de702a1b5e59b15e9afe6c1eb4e))
- **core:** ensure input item always have a name
([#&#8203;1407](https://github.com/rolldown/rolldown/issues/1407))
([0e6afa2](https://github.com/rolldown/rolldown/commit/0e6afa2fe9047ffba847287a98d93f218ca590ab))
- export more typing
([#&#8203;1420](https://github.com/rolldown/rolldown/issues/1420))
([9854330](https://github.com/rolldown/rolldown/commit/9854330074c1851872688fe3fa7a29f36cd6a011))
- export more typing to compat rollup
([#&#8203;1418](https://github.com/rolldown/rolldown/issues/1418))
([949c819](https://github.com/rolldown/rolldown/commit/949c81960859dfaf7f83f0f468042b4bf1c36f30))
- **inner:** add `NormalModule#module_type`
([#&#8203;1448](https://github.com/rolldown/rolldown/issues/1448))
([449dcce](https://github.com/rolldown/rolldown/commit/449dcce6ce907c2233997af8ee5cb658ed9c9e6e))
- mark `PluginContext#parse` as unsupported
([#&#8203;1289](https://github.com/rolldown/rolldown/issues/1289))
([aef45e0](https://github.com/rolldown/rolldown/commit/aef45e09fa93e7df8f18422fb8d5c47fae0c77f0))
- **ModuleType:** support `empty`
([#&#8203;1369](https://github.com/rolldown/rolldown/issues/1369))
([cb3bf33](https://github.com/rolldown/rolldown/commit/cb3bf33f69a303b50ffcaa04ebfa1d31c1a4a17d))
- move dependency
([#&#8203;1381](https://github.com/rolldown/rolldown/issues/1381))
([1f70a4c](https://github.com/rolldown/rolldown/commit/1f70a4cd7b7dc0d78d0cf446bfd77b851c4c1a25))
- **node:** expose the `moduleTypes` option
([#&#8203;1451](https://github.com/rolldown/rolldown/issues/1451))
([39f16e2](https://github.com/rolldown/rolldown/commit/39f16e2459dccc07fb793c421ff8c38096a5061b))
- oxc v0.15.0
([#&#8203;1415](https://github.com/rolldown/rolldown/issues/1415))
([39761b0](https://github.com/rolldown/rolldown/commit/39761b0004545338881273b6b43aebe2071450d9))
- **rust:** add `AllocatorExt` trait
([#&#8203;1350](https://github.com/rolldown/rolldown/issues/1350))
([fa4262c](https://github.com/rolldown/rolldown/commit/fa4262c85875c02bec15114e2430fb79850bb33a))
- support `outputOptions` hook
([#&#8203;1339](https://github.com/rolldown/rolldown/issues/1339))
([176ca26](https://github.com/rolldown/rolldown/commit/176ca26c0c3b6cb262a37db6881c3ad8349ae3df))
- support base64 loader
([#&#8203;1352](https://github.com/rolldown/rolldown/issues/1352))
([16d5938](https://github.com/rolldown/rolldown/commit/16d59384099db5f1927144a3de501813bd79e39d))
- support binary loader
([#&#8203;1365](https://github.com/rolldown/rolldown/issues/1365))
([8f2e07b](https://github.com/rolldown/rolldown/commit/8f2e07b54dbfe8f49722f9e01c6f1ca26b824b99))
- support emit binary asset
([#&#8203;1359](https://github.com/rolldown/rolldown/issues/1359))
([cfc16e8](https://github.com/rolldown/rolldown/commit/cfc16e801f899359f16ea2c53ca2b94da168453a))
- support PluginContext emit asset
([#&#8203;1349](https://github.com/rolldown/rolldown/issues/1349))
([da183aa](https://github.com/rolldown/rolldown/commit/da183aabcfdf6bdbf5abf79398b70cacccc04d4c))
- support RenderedChunk#name
([#&#8203;1421](https://github.com/rolldown/rolldown/issues/1421))
([a64e78f](https://github.com/rolldown/rolldown/commit/a64e78f31e13e3da38dd68fede711b872c0c8d6b))
- tree shake module side effect
([#&#8203;1395](https://github.com/rolldown/rolldown/issues/1395))
([6df56a9](https://github.com/rolldown/rolldown/commit/6df56a90b61a297c2e287f7e7fc614464d9cfc9c))
- wasm plugin
([#&#8203;1368](https://github.com/rolldown/rolldown/issues/1368))
([65ec42c](https://github.com/rolldown/rolldown/commit/65ec42c4b7a50e0ce9e8d491e9c37c6a4203e168))

###
[`v0.10.4`](https://github.com/rolldown/rolldown/blob/HEAD/CHANGELOG.md#0104-2024-06-04)

##### Bug Fixes

- add return source logic when file not downloaded and add loader …
([#&#8203;1287](https://github.com/rolldown/rolldown/issues/1287))
([103b8e5](https://github.com/rolldown/rolldown/commit/103b8e50d92c5fafea36e830a62ffb627c4d4f9e))
- **cjs:** distinguish if symbols are referenced by chunk or modules
([#&#8203;1316](https://github.com/rolldown/rolldown/issues/1316))
([75c69b3](https://github.com/rolldown/rolldown/commit/75c69b322711e738bb367a0d7d73f2c738943013))
- **cjs:** should render runtime module before generated imports
([#&#8203;1335](https://github.com/rolldown/rolldown/issues/1335))
([94b1371](https://github.com/rolldown/rolldown/commit/94b137111b28d92684725cc24dd2e944f25c0ab1))
- **deps:** update dependency debug to v4.3.5
([#&#8203;1296](https://github.com/rolldown/rolldown/issues/1296))
([95460de](https://github.com/rolldown/rolldown/commit/95460de45ddb8d825fd544a4a2399822b55068d9))

##### Features

- **app:** rewrite static import
([#&#8203;1323](https://github.com/rolldown/rolldown/issues/1323))
([68c6592](https://github.com/rolldown/rolldown/commit/68c6592d6986cdb53bef1c33159c5bad6314bcd8))
- **app:** use `IsolatingModuleFinalizer` for app output
([#&#8203;1317](https://github.com/rolldown/rolldown/issues/1317))
([92bfe2d](https://github.com/rolldown/rolldown/commit/92bfe2d6d27ec313d5afcca0207d0847eba1e681))
- **cjs:** add `__esModule` flag
([#&#8203;1313](https://github.com/rolldown/rolldown/issues/1313))
([d892948](https://github.com/rolldown/rolldown/commit/d892948c77e1815f4ce9b224c0711ca63bdb594e))
- **cjs:** add `"use strict"` if possible
([#&#8203;1284](https://github.com/rolldown/rolldown/issues/1284))
([bf3f86e](https://github.com/rolldown/rolldown/commit/bf3f86e09058fc34ab281fc232ea9fd031d2e07d))
- **output:** make output folding-friendly using `#region`
([#&#8203;1330](https://github.com/rolldown/rolldown/issues/1330))
([ace105c](https://github.com/rolldown/rolldown/commit/ace105cf69965baec8ac1626d5b79e42b66574e3))
- **plugin:** support `options` hook
([#&#8203;1275](https://github.com/rolldown/rolldown/issues/1275))
([fc94245](https://github.com/rolldown/rolldown/commit/fc9424582f34fc540d285aa40f3aa1d95d1ddd23))
- **plugin:** support return `sideEffect: 'no-treeshake'`
([#&#8203;1293](https://github.com/rolldown/rolldown/issues/1293))
([283a58c](https://github.com/rolldown/rolldown/commit/283a58c1fdb5db1bb98458abd9c7570124c8c776))
- remove `use strict` while emitting esm output
([#&#8203;1283](https://github.com/rolldown/rolldown/issues/1283))
([79fbbd4](https://github.com/rolldown/rolldown/commit/79fbbd4e5357335ea07f2f63041c47e17dd77e6b))
- **rust/options:** add `BundlerOptions#loaders`
([#&#8203;1280](https://github.com/rolldown/rolldown/issues/1280))
([804df07](https://github.com/rolldown/rolldown/commit/804df07c57a5d9be1b299b9facd0fdff132c55a3))
- **rust:** deny invalid parsing code
([#&#8203;1310](https://github.com/rolldown/rolldown/issues/1310))
([5be6ffb](https://github.com/rolldown/rolldown/commit/5be6ffb1b157780879dfcf4a96d0db15c3861ba0))
- support text loader
([#&#8203;1302](https://github.com/rolldown/rolldown/issues/1302))
([b0f19c1](https://github.com/rolldown/rolldown/commit/b0f19c1f203a45f8a300028cbfe8cd38a77d95b4))

</details>

<details>
<summary>oxc-project/oxc (oxlint)</summary>

###
[`v0.5.1`](https://github.com/oxc-project/oxc/releases/tag/oxlint_v0.5.1):
oxlint v0.5.1

[Compare
Source](https://github.com/oxc-project/oxc/compare/1d74db77741829f2abce0b01d24135947b284c2b...21b964b214758d8fe3685ca2a6515cb4742a26e3)

#### \[0.5.1] - 2024-06-29

##### Bug Fixes

- [`c26975a`](https://github.com/oxc-project/oxc/commit/c26975a)
linter: Only show the filename for max-lines
([#&#8203;3966](https://github.com/oxc-project/oxc/issues/3966))
(Boshen)
- [`94329e4`](https://github.com/oxc-project/oxc/commit/94329e4)
linter: Handle useful but empty constructors in no-useless-constructor
([#&#8203;3951](https://github.com/oxc-project/oxc/issues/3951))
(DonIsaac)
- [`6498a08`](https://github.com/oxc-project/oxc/commit/6498a08)
linter: No-useless-spread fixer with multiple spread elements
([#&#8203;3950](https://github.com/oxc-project/oxc/issues/3950))
(DonIsaac)

###
[`v0.5.0`](https://github.com/oxc-project/oxc/releases/tag/oxlint_v0.5.0):
oxlint v0.5.0

[Compare
Source](https://github.com/oxc-project/oxc/compare/2173f23d9cbda547135000a3a00cd7b2e18dc762...1d74db77741829f2abce0b01d24135947b284c2b)

#### \[0.5.0] - 2024-06-27

##### Features

- [`3ae2628`](https://github.com/oxc-project/oxc/commit/3ae2628)
linter: Change `no-import-assign` to correctness
([#&#8203;3928](https://github.com/oxc-project/oxc/issues/3928))
(Boshen)
- [`a89d501`](https://github.com/oxc-project/oxc/commit/a89d501)
linter:
[@&#8203;typescript-eslint/no-non-null-asserted-nullish-coalescing](https://github.com/typescript-eslint/no-non-null-asserted-nullish-coalescing)
([#&#8203;3850](https://github.com/oxc-project/oxc/issues/3850))
(kaykdm)
- [`fc48cb4`](https://github.com/oxc-project/oxc/commit/fc48cb4)
linter: eslint-plugin-jest/prefer-jest-mocked
([#&#8203;3865](https://github.com/oxc-project/oxc/issues/3865))
(cinchen)
- [`328445b`](https://github.com/oxc-project/oxc/commit/328445b)
linter: vitest/no-disabled-tests
([#&#8203;3717](https://github.com/oxc-project/oxc/issues/3717))
(mysteryven)
- [`8c61f9c`](https://github.com/oxc-project/oxc/commit/8c61f9c)
linter:
[@&#8203;typescript-eslint/no-non-null-assertion](https://github.com/typescript-eslint/no-non-null-assertion)
([#&#8203;3825](https://github.com/oxc-project/oxc/issues/3825))
(kaykdm)
- [`9493fbe`](https://github.com/oxc-project/oxc/commit/9493fbe)
linter: oxc/no-optional-chaining
([#&#8203;3700](https://github.com/oxc-project/oxc/issues/3700))
(mysteryven)
- [`139adfe`](https://github.com/oxc-project/oxc/commit/139adfe)
linter: @&#8203;typescript-eslint/no-import-type-side_effects
([#&#8203;3699](https://github.com/oxc-project/oxc/issues/3699))
(mysteryven)
- [`5f84500`](https://github.com/oxc-project/oxc/commit/5f84500)
linter: react/prefer-es6-class
([#&#8203;3812](https://github.com/oxc-project/oxc/issues/3812))
(Jelle van der Waa)
- [`fafe67c`](https://github.com/oxc-project/oxc/commit/fafe67c)
linter: max-dependencies
([#&#8203;3814](https://github.com/oxc-project/oxc/issues/3814))
(Jelle van der Waa)

##### Bug Fixes

- [`5902331`](https://github.com/oxc-project/oxc/commit/5902331) cli:
properly report configuration error
([#&#8203;3889](https://github.com/oxc-project/oxc/issues/3889)) (Luca
Bruno)

##### Refactor

- [`7302429`](https://github.com/oxc-project/oxc/commit/7302429)
linter/prefer_number_properties: Remove the unused `IdentifierName`
check ([#&#8203;3822](https://github.com/oxc-project/oxc/issues/3822))
(Boshen)

</details>

<details>
<summary>pnpm/pnpm (pnpm)</summary>

### [`v9.4.0`](https://github.com/pnpm/pnpm/compare/v9.3.0...v9.4.0)

[Compare Source](https://github.com/pnpm/pnpm/compare/v9.3.0...v9.4.0)

</details>

<details>
<summary>Microsoft/TypeScript (typescript)</summary>

###
[`v5.5.2`](https://github.com/Microsoft/TypeScript/compare/v5.4.5...ce2e60e4ea15a65992e54a9e8877d16be9d42abb)

[Compare
Source](https://github.com/Microsoft/TypeScript/compare/v5.4.5...v5.5.2)

</details>

<details>
<summary>vitejs/vite (vite)</summary>

###
[`v5.3.2`](https://github.com/vitejs/vite/blob/HEAD/packages/vite/CHANGELOG.md#small532-2024-06-27-small)

[Compare
Source](https://github.com/vitejs/vite/compare/v5.3.1...v5.3.2)

- fix(client): uniform variable `location`
([#&#8203;17528](https://github.com/vitejs/vite/issues/17528))
([a8e2f6f](https://github.com/vitejs/vite/commit/a8e2f6f)), closes
[#&#8203;17528](https://github.com/vitejs/vite/issues/17528)
- fix(deps): update all non-major dependencies
([#&#8203;17494](https://github.com/vitejs/vite/issues/17494))
([bf123f2](https://github.com/vitejs/vite/commit/bf123f2)), closes
[#&#8203;17494](https://github.com/vitejs/vite/issues/17494)
- fix(typescript): correctly expand ${configDir} in tsconfig.json
([#&#8203;17576](https://github.com/vitejs/vite/issues/17576))
([24c799b](https://github.com/vitejs/vite/commit/24c799b)), closes
[#&#8203;17576](https://github.com/vitejs/vite/issues/17576)
- chore: fix some comments
([#&#8203;17495](https://github.com/vitejs/vite/issues/17495))
([ec16a5e](https://github.com/vitejs/vite/commit/ec16a5e)), closes
[#&#8203;17495](https://github.com/vitejs/vite/issues/17495)
- chore(deps): update all non-major dependencies
([#&#8203;17553](https://github.com/vitejs/vite/issues/17553))
([a33a97f](https://github.com/vitejs/vite/commit/a33a97f)), closes
[#&#8203;17553](https://github.com/vitejs/vite/issues/17553)
- chore(deps): update dependency eslint to v9
([#&#8203;16661](https://github.com/vitejs/vite/issues/16661))
([6c10662](https://github.com/vitejs/vite/commit/6c10662)), closes
[#&#8203;16661](https://github.com/vitejs/vite/issues/16661)
- chore(deps): update es-module-lexer to 1.5.4
([#&#8203;17555](https://github.com/vitejs/vite/issues/17555))
([2d6672f](https://github.com/vitejs/vite/commit/2d6672f)), closes
[#&#8203;17555](https://github.com/vitejs/vite/issues/17555)
- refactor(optimizer): use early continues
([#&#8203;17551](https://github.com/vitejs/vite/issues/17551))
([7c06ef0](https://github.com/vitejs/vite/commit/7c06ef0)), closes
[#&#8203;17551](https://github.com/vitejs/vite/issues/17551)

</details>

<details>
<summary>vuejs/core (vue)</summary>

###
[`v3.4.31`](https://github.com/vuejs/core/blob/HEAD/CHANGELOG.md#3431-2024-06-28)

[Compare
Source](https://github.com/vuejs/core/compare/v3.4.30...v3.4.31)

##### Bug Fixes

- **compiler-core:** handle inline comments with undefined bindings
([#&#8203;11217](https://github.com/vuejs/core/issues/11217))
([746352a](https://github.com/vuejs/core/commit/746352a14d62e9d3d9a38c359d2c54d418c1e0ac)),
closes [#&#8203;11216](https://github.com/vuejs/core/issues/11216)
- **shared:** unwrap refs in toDisplayString
([#&#8203;7306](https://github.com/vuejs/core/issues/7306))
([0126cff](https://github.com/vuejs/core/commit/0126cfff9d93bcec70e5745519f6378e3cd3f39c)),
closes [#&#8203;5578](https://github.com/vuejs/core/issues/5578)
[#&#8203;5593](https://github.com/vuejs/core/issues/5593)
[#&#8203;11199](https://github.com/vuejs/core/issues/11199)
[#&#8203;11201](https://github.com/vuejs/core/issues/11201)

##### Reverts

- Revert "fix(reactivity): avoid infinite loop when render access a side
effect computed
([#&#8203;11135](https://github.com/vuejs/core/issues/11135))"
([e0df985](https://github.com/vuejs/core/commit/e0df985f0317fb65c5b461bf224375c7763f0269))
- Revert "fix(reactivity): fix side effect computed dirty level
([#&#8203;11183](https://github.com/vuejs/core/issues/11183))"
([6c303ea](https://github.com/vuejs/core/commit/6c303eacd14b7b0de0accc228f6abeb43d706f63)),
closes [#&#8203;11183](https://github.com/vuejs/core/issues/11183)

###
[`v3.4.30`](https://github.com/vuejs/core/blob/HEAD/CHANGELOG.md#3430-2024-06-22)

[Compare
Source](https://github.com/vuejs/core/compare/v3.4.29...v3.4.30)

##### Bug Fixes

- **compiler-core:** should not remove slot node with `v-else`
([#&#8203;11150](https://github.com/vuejs/core/issues/11150))
([e102670](https://github.com/vuejs/core/commit/e102670bde00417c3a5b0262c855b297c0e4169e))
- **hydration:** fix css vars hydration mismatch false positive on
attr-fallthrough
([#&#8203;11190](https://github.com/vuejs/core/issues/11190))
([7ad67ce](https://github.com/vuejs/core/commit/7ad67ced26e5f53a47cb42f4834496e4958cb53b)),
closes [#&#8203;11188](https://github.com/vuejs/core/issues/11188)
- **hydration:** skip prop mismatch check for directives that mutate DOM
in created
([3169c91](https://github.com/vuejs/core/commit/3169c914939d02a013b2938aff30dac8525923f8)),
closes [#&#8203;11189](https://github.com/vuejs/core/issues/11189)
- **reactivity:** fix side effect computed dirty level
([#&#8203;11183](https://github.com/vuejs/core/issues/11183))
([3bd79e3](https://github.com/vuejs/core/commit/3bd79e3e5ed960fc42cbf77bc61a97d2c03557c0)),
closes [#&#8203;11181](https://github.com/vuejs/core/issues/11181)
[#&#8203;11169](https://github.com/vuejs/core/issues/11169)
- **runtime-core:** ensure unmount dynamic components in optimized mode
([#&#8203;11171](https://github.com/vuejs/core/issues/11171))
([220fe24](https://github.com/vuejs/core/commit/220fe247484209e62c7f4991902c5335e29c5007)),
closes [#&#8203;11168](https://github.com/vuejs/core/issues/11168)
- **runtime-core:** update devtool \__vnode on patch, avoid memory leak
during dev
([a959781](https://github.com/vuejs/core/commit/a959781dd6f609dcb6f16dd7fa47d3b16895e5ca)),
closes [#&#8203;11192](https://github.com/vuejs/core/issues/11192)
- **runtime-dom:** ensure only symbols are explicitly stringified during
attribute patching
([#&#8203;11182](https://github.com/vuejs/core/issues/11182))
([a2e35d6](https://github.com/vuejs/core/commit/a2e35d682db15a592f4270bb0cde70a0e7bdc4a6)),
closes [#&#8203;11177](https://github.com/vuejs/core/issues/11177)
- **runtime-dom:** prevent setting state as attribute for custom
elements ([#&#8203;11165](https://github.com/vuejs/core/issues/11165))
([8ae4c29](https://github.com/vuejs/core/commit/8ae4c293adcec28f18114cb6016230a86787e6a9)),
closes [#&#8203;11163](https://github.com/vuejs/core/issues/11163)

##### Performance Improvements

- **reactivity:** cache tracking value
([#&#8203;11145](https://github.com/vuejs/core/issues/11145))
([7936dae](https://github.com/vuejs/core/commit/7936daebceab2ae9461c3b8f256e51020fb7d3ed))

</details>

<details>
<summary>vuejs/router (vue-router)</summary>

### [`v4.4.0`](https://github.com/vuejs/router/releases/tag/v4.4.0)

[Compare
Source](https://github.com/vuejs/router/compare/v4.3.3...v4.4.0)

Please refer to
[CHANGELOG.md](https://github.com/vuejs/router/blob/main/packages/router/CHANGELOG.md)
for details.

</details>

<details>
<summary>google/zx (zx)</summary>

### [`v8.1.3`](https://github.com/google/zx/releases/tag/8.1.3)

[Compare Source](https://github.com/google/zx/compare/8.1.2...8.1.3)

Nothing special today. We just keep improving the implementation.

#### Features

- ESM support is now available for Node.js v12 (previously was cjs
only): <br/><sup>[#&#8203;824](https://github.com/google/zx/pull/824),
[#&#8203;827](https://github.com/google/zx/pull/827),
[#&#8203;828](https://github.com/google/zx/pull/828)</sup>

```ts
import {$} from 'zx'
```

-   `zx/cli` exports its inners to allow more advanced usage.
Imagine, your own CLI tool that uses `zx` as a base:
<br/><sup>[#&#8203;828](https://github.com/google/zx/pull/838)</sup>

```ts

#!/usr/bin/env node

import './index.mjs'
import {main} from 'zx/cli'

main()
```

- Provide intermediate store configuration for fine-grained control of
memory usage.
<br/><sup>[#&#8203;650](https://github.com/google/zx/pull/650),
[#&#8203;849](https://github.com/google/zx/pull/849)</sup>

```ts
const getFixedSizeArray = (size) => {
  const arr = []
  return new Proxy(arr, {
    get: (target, prop) =>
      prop === 'push' && arr.length >= size
        ? () => {}
        : target[prop],
  })
}
const store = {
  stdout: getFixedSizeArray(1),
  stderr: getFixedSizeArray(1),
  stdall: getFixedSizeArray(0),
}

const p = await $({ store })`echo foo`

p.stdout.trim() //  'foo'
p.toString()    // ''
```

- Introduced sync methods for `ps`:
<br/><sup>[#&#8203;840](https://github.com/google/zx/pull/840)</sup>

```ts
import { ps } from 'zx'

const list1 = await ps()
const list2 = await tree()

// new methods
const list3 = ps.sync()
const list4 = tree.sync()
```

#### Chore

- `$.log` accepts `kind: 'custom'`
[#&#8203;834](https://github.com/google/zx/pull/834)
- Describe [`$.verbose` and `$.quiet` modes
internals](https://google.github.io/zx/faq#verbose-and-quiet)
[#&#8203;835](https://github.com/google/zx/pull/835)
- Mention `quotePowerShell` in docs
[#&#8203;851](https://github.com/google/zx/pull/851)
- Finally fixed the annoying flaky problem of the process end detection
in Bun [#&#8203;839](https://github.com/google/zx/pull/839),
[coderef](https://github.com/webpod/zurk/pull/10/files#diff-d32293984327495f7762a47d34fd13d89e57732be64a76d01b1d5edd6c2d316cR185)
- Suppress `async_hooks.createHook` warning on bun
[#&#8203;848](https://github.com/google/zx/pull/848)
- Remove node-abort-controller in favor of built-in node-fetch polyfill
[#&#8203;842](https://github.com/google/zx/pull/842)
- Add missing global types
[#&#8203;853](https://github.com/google/zx/pull/853)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 10am on monday" in timezone
Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config help](https://github.com/renovatebot/renovate/discussions) if
that's undesired.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/rolldown/rolldown).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
keithamus pushed a commit to keithamus/hdx that referenced this pull request Jul 1, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Type | Update | Change | Age | Adoption | Passing |
Confidence |
|---|---|---|---|---|---|---|---|
| [clap](https://github.com/clap-rs/clap) | workspace.dependencies |
patch | `4.5.7` -> `4.5.8` |
[![age](https://developer.mend.io/api/mc/badges/age/crate/clap/4.5.8?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/crate/clap/4.5.8?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/crate/clap/4.5.7/4.5.8?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/crate/clap/4.5.7/4.5.8?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [esbuild](https://github.com/evanw/esbuild) | devDependencies |
minor | [`^0.21.0` ->
`^0.22.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.5/0.22.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.5/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.5/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [serde_json](https://github.com/serde-rs/json) |
workspace.dependencies | patch | `1.0.117` -> `1.0.119` |
[![age](https://developer.mend.io/api/mc/badges/age/crate/serde_json/1.0.119?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/crate/serde_json/1.0.119?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/crate/serde_json/1.0.117/1.0.119?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/crate/serde_json/1.0.117/1.0.119?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>clap-rs/clap (clap)</summary>

###
[`v4.5.8`](https://github.com/clap-rs/clap/blob/HEAD/CHANGELOG.md#458---2024-06-28)

[Compare
Source](https://github.com/clap-rs/clap/compare/v4.5.7...v4.5.8)

##### Fixes

-   Reduce extra flushes

</details>

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

</details>

<details>
<summary>serde-rs/json (serde_json)</summary>

###
[`v1.0.119`](https://github.com/serde-rs/json/releases/tag/v1.0.119)

[Compare
Source](https://github.com/serde-rs/json/compare/v1.0.118...v1.0.119)

- Add `serde_json::Map::shift_insert`
([#&#8203;1149](https://github.com/serde-rs/json/issues/1149), thanks
[@&#8203;joshka](https://github.com/joshka))

###
[`v1.0.118`](https://github.com/serde-rs/json/releases/tag/v1.0.118)

[Compare
Source](https://github.com/serde-rs/json/compare/v1.0.117...v1.0.118)

- Implement Hash for serde_json::Value
([#&#8203;1127](https://github.com/serde-rs/json/issues/1127), thanks
[@&#8203;edwardycl](https://github.com/edwardycl))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 9am on monday" (UTC),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config help](https://github.com/renovatebot/renovate/discussions) if
that's undesired.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/keithamus/hdx).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
gr2m pushed a commit to octokit/rest.js that referenced this pull request Jul 1, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [esbuild](https://github.com/evanw/esbuild) | [`^0.21.0` ->
`^0.22.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.5/0.22.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.5/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.5/0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/octokit/rest.js).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUeXBlOiBNYWludGVuYW5jZSJdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
netbsd-srcmastr pushed a commit to NetBSD/pkgsrc that referenced this pull request Jul 1, 2024
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.21.0 or
~0.21.0. See npm's documentation about semver for more information.

  * Omit packages from bundles by default when targeting node

    This breaking change is an experiment. People are commonly confused when
    using esbuild to bundle code for node (i.e. for --platform=node) because
    some packages may not be intended for bundlers, and may use node-specific
    features that don't work with a bundler. Even though esbuild's "getting
    started" instructions say to use --packages=external to work around this
    problem, many people don't read the documentation and don't do this, and
    are then confused when it doesn't work. So arguably this is a bad default
    behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by
    default when the platform is node (i.e. the previous behavior of --packages
    =external is now the default in this case). Note that your dependencies
    must now be present on the file system when your bundle is run. If you
    don't want this behavior, you can do --packages=bundle to allow packages to
    be included in the bundle (i.e. the previous default behavior). Note that
    --packages=bundle doesn't mean all packages are bundled, just that packages
    are allowed to be bundled. You can still exclude individual packages from
    the bundle using --external: even when --packages=bundle is present.

    The --packages= setting considers all import paths that "look like" package
    imports in the original source code to be package imports. Specifically
    import paths that don't start with a path segment of / or . or .. are
    considered to be package imports. The only two exceptions to this rule are
    subpath imports (which start with a # character) and TypeScript path
    remappings via paths and/or baseUrl in tsconfig.json (which are applied
    first).

  * Update await using behavior to match TypeScript

    TypeScript 5.5 subtly changes the way await using behaves. This release
    updates esbuild to match these changes in TypeScript. You can read more
    about these changes in microsoft/TypeScript#58624.

  * Allow es2024 as a target environment

    The ECMAScript 2024 specification was just approved, so it has been added
    to esbuild as a possible compilation target. You can read more about the
    features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html
    . The only addition that's relevant for esbuild is the regular expression /
    v flag. With --target=es2024, regular expressions that use the /v flag will
    now be passed through untransformed instead of being transformed into a
    call to new RegExp.

  * Publish binaries for WASI (WebAssembly System Interface) preview 1

    The upcoming WASI (WebAssembly System Interface) standard is going to be a
    way to run WebAssembly outside of a JavaScript host environment. In this
    scenario you only need a .wasm file without any supporting JavaScript code.
    Instead of JavaScript providing the APIs for the host environment, the WASI
    standard specifies a "system interface" that WebAssembly code can access
    directly (e.g. for file system access).

    Development versions of the WASI specification are being released using
    preview numbers. The people behind WASI are currently working on preview 2
    but the Go compiler has released support for preview 1, which from what I
    understand is now considered an unsupported legacy release. However, some
    people have requested that esbuild publish binary executables that support
    WASI preview 1 so they can experiment with them.

    This release publishes esbuild precompiled for WASI preview 1 to the
    @esbuild/wasi-preview1 package on npm (specifically the file @esbuild/
    wasi-preview1/esbuild.wasm). This binary executable has not been tested and
    won't be officially supported, as it's for an old preview release of a
    specification that has since moved in another direction. If it works for
    you, great! If not, then you'll likely have to wait for the ecosystem to
    evolve before using esbuild with WASI. For example, it sounds like perhaps
    WASI preview 1 doesn't include support for opening network sockets so
    esbuild's local development server is unlikely to work with WASI preview 1.

  * Warn about onResolve plugins not setting a path

    Plugins that return values from onResolve without resolving the path (i.e.
    without setting either path or external: true) will now cause a warning.
    This is because esbuild only uses return values from onResolve if it
    successfully resolves the path, and it's not good for invalid input to be
    silently ignored.

  * Add a new Go API for running the CLI with plugins

    With esbuild's Go API, you can now call cli.RunWithPlugins(args, plugins)
    to pass an array of esbuild plugins to be used during the build process.
    This allows you to create a CLI that behaves similarly to esbuild's CLI but
    with additional Go plugins enabled.
renovate bot added a commit to JoshuaKGoldberg/refined-saved-replies that referenced this pull request Jul 5, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [esbuild](https://github.com/evanw/esbuild) | [`^0.21.0` ->
`^0.23.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.5/0.23.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.23.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.22.0...v0.23.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.22.0` or `~0.22.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Revert the recent change to avoid bundling dependencies for node
([#&#8203;3819](https://github.com/evanw/esbuild/issues/3819))

This release reverts the recent change in version 0.22.0 that made
`--packages=external` the default behavior with `--platform=node`. The
default is now back to `--packages=bundle`.

I've just been made aware that Amazon doesn't pin their dependencies in
their "AWS CDK" product, which means that whenever esbuild publishes a
new release, many people (potentially everyone?) using their SDK around
the world instantly starts using it without Amazon checking that it
works first. This change in version 0.22.0 happened to break their SDK.
I'm amazed that things haven't broken before this point. This revert
attempts to avoid these problems for Amazon's customers. Hopefully
Amazon will pin their dependencies in the future.

In addition, this is probably a sign that esbuild is used widely enough
that it now needs to switch to a more complicated release model. I may
have esbuild use a beta channel model for further development.

- Fix preserving collapsed JSX whitespace
([#&#8203;3818](https://github.com/evanw/esbuild/issues/3818))

When transformed, certain whitespace inside JSX elements is ignored
completely if it collapses to an empty string. However, the whitespace
should only be ignored if the JSX is being transformed, not if it's
being preserved. This release fixes a bug where esbuild was previously
incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is
an example:

    ```jsx
    // Original code
    <Foo>
      <Bar />
    </Foo>

    // Old output (with --jsx=preserve)
    <Foo><Bar /></Foo>;

    // New output (with --jsx=preserve)
    <Foo>
      <Bar />
    </Foo>;
    ```

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/JoshuaKGoldberg/refined-saved-replies).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuOSIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS45IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
mergify bot pushed a commit to SvenKirschbaum/aws-utils that referenced this pull request Jul 6, 2024
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Type | Update | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|---|---|
|  |  | lockFileMaintenance | All locks refreshed |  |  |  |  |
| [@aws-sdk/client-secrets-manager](https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-secrets-manager) ([source](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-secrets-manager)) | dependencies | minor | [`3.606.0` -> `3.609.0`](https://renovatebot.com/diffs/npm/@aws-sdk%2fclient-secrets-manager/3.606.0/3.609.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@aws-sdk%2fclient-secrets-manager/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@aws-sdk%2fclient-secrets-manager/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@aws-sdk%2fclient-secrets-manager/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@aws-sdk%2fclient-secrets-manager/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/core](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/core)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fcore/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fcore/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fcore/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fcore/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fcore/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/error-logger](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/error-logger)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2ferror-logger/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2ferror-logger/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2ferror-logger/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2ferror-logger/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2ferror-logger/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-content-negotiation](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-content-negotiation)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-content-negotiation/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-content-negotiation/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-content-negotiation/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-content-negotiation/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-content-negotiation/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-error-handler](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-error-handler)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-error-handler/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-error-handler/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-error-handler/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-error-handler/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-error-handler/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-header-normalizer](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-header-normalizer)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-header-normalizer/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-header-normalizer/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-header-normalizer/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-header-normalizer/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-header-normalizer/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-json-body-parser](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-json-body-parser)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-json-body-parser/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-json-body-parser/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-json-body-parser/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-json-body-parser/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-json-body-parser/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-response-serializer](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-response-serializer)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-response-serializer/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-response-serializer/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-response-serializer/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-response-serializer/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-response-serializer/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@mui/icons-material](https://mui.com/material-ui/material-icons/) ([source](https://github.com/mui/material-ui/tree/HEAD/packages/mui-icons-material)) | dependencies | minor | [`5.15.21` -> `5.16.0`](https://renovatebot.com/diffs/npm/@mui%2ficons-material/5.15.21/5.16.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@mui%2ficons-material/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@mui%2ficons-material/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@mui%2ficons-material/5.15.21/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@mui%2ficons-material/5.15.21/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@mui/material](https://mui.com/material-ui/) ([source](https://github.com/mui/material-ui/tree/HEAD/packages/mui-material)) | dependencies | minor | [`5.15.21` -> `5.16.0`](https://renovatebot.com/diffs/npm/@mui%2fmaterial/5.15.21/5.16.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@mui%2fmaterial/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@mui%2fmaterial/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@mui%2fmaterial/5.15.21/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@mui%2fmaterial/5.15.21/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@mui/x-data-grid](https://mui.com/x/react-data-grid/) ([source](https://github.com/mui/mui-x/tree/HEAD/packages/x-data-grid)) | dependencies | minor | [`7.8.0` -> `7.9.0`](https://renovatebot.com/diffs/npm/@mui%2fx-data-grid/7.8.0/7.9.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@mui%2fx-data-grid/7.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@mui%2fx-data-grid/7.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@mui%2fx-data-grid/7.8.0/7.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@mui%2fx-data-grid/7.8.0/7.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@trautonen/cdk-dns-validated-certificate](https://github.com/trautonen/cdk-dns-validated-certificate) | dependencies | patch | [`0.1.3` -> `0.1.4`](https://renovatebot.com/diffs/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.3/0.1.4) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.3/0.1.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.3/0.1.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | devDependencies | patch | [`20.14.9` -> `20.14.10`](https://renovatebot.com/diffs/npm/@types%2fnode/20.14.9/20.14.10) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2fnode/20.14.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@types%2fnode/20.14.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@types%2fnode/20.14.9/20.14.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2fnode/20.14.9/20.14.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@typescript-eslint/eslint-plugin](https://typescript-eslint.io/packages/eslint-plugin) ([source](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin)) | devDependencies | minor | [`7.14.1` -> `7.15.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2feslint-plugin/7.14.1/7.15.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@typescript-eslint%2feslint-plugin/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@typescript-eslint%2feslint-plugin/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@typescript-eslint%2feslint-plugin/7.14.1/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@typescript-eslint%2feslint-plugin/7.14.1/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [aws-cdk](https://github.com/aws/aws-cdk) ([source](https://github.com/aws/aws-cdk/tree/HEAD/packages/aws-cdk)) | devDependencies | minor | [`2.147.2` -> `2.148.0`](https://renovatebot.com/diffs/npm/aws-cdk/2.147.2/2.148.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/aws-cdk/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/aws-cdk/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/aws-cdk/2.147.2/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/aws-cdk/2.147.2/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [aws-cdk-lib](https://github.com/aws/aws-cdk) ([source](https://github.com/aws/aws-cdk/tree/HEAD/packages/aws-cdk-lib)) | dependencies | minor | [`2.147.2` -> `2.148.0`](https://renovatebot.com/diffs/npm/aws-cdk-lib/2.147.2/2.148.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/aws-cdk-lib/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/aws-cdk-lib/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/aws-cdk-lib/2.147.2/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/aws-cdk-lib/2.147.2/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [esbuild](https://github.com/evanw/esbuild) | devDependencies | minor | [`0.21.5` -> `0.23.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.5/0.23.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [typescript](https://www.typescriptlang.org/) ([source](https://github.com/Microsoft/TypeScript)) | devDependencies | patch | [`5.5.2` -> `5.5.3`](https://renovatebot.com/diffs/npm/typescript/5.5.2/5.5.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/typescript/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/typescript/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/typescript/5.5.2/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/typescript/5.5.2/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@typescript-eslint/parser](https://typescript-eslint.io/packages/parser) ([source](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser)) | devDependencies | minor | [`7.14.1` -> `7.15.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2fparser/7.14.1/7.15.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@typescript-eslint%2fparser/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@typescript-eslint%2fparser/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@typescript-eslint%2fparser/7.14.1/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@typescript-eslint%2fparser/7.14.1/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [react-router](https://github.com/remix-run/react-router) ([source](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router)) | dependencies | patch | [`6.24.0` -> `6.24.1`](https://renovatebot.com/diffs/npm/react-router/6.24.0/6.24.1) | [![age](https://developer.mend.io/api/mc/badges/age/npm/react-router/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/react-router/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/react-router/6.24.0/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/react-router/6.24.0/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [react-router-dom](https://github.com/remix-run/react-router) ([source](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom)) | dependencies | patch | [`6.24.0` -> `6.24.1`](https://renovatebot.com/diffs/npm/react-router-dom/6.24.0/6.24.1) | [![age](https://developer.mend.io/api/mc/badges/age/npm/react-router-dom/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/react-router-dom/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/react-router-dom/6.24.0/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/react-router-dom/6.24.0/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [typescript](https://www.typescriptlang.org/) ([source](https://github.com/Microsoft/TypeScript)) | dependencies | patch | [`5.5.2` -> `5.5.3`](https://renovatebot.com/diffs/npm/typescript/5.5.2/5.5.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/typescript/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/typescript/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/typescript/5.5.2/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/typescript/5.5.2/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [vite](https://vitejs.dev) ([source](https://github.com/vitejs/vite/tree/HEAD/packages/vite)) | devDependencies | patch | [`5.3.2` -> `5.3.3`](https://renovatebot.com/diffs/npm/vite/5.3.2/5.3.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/vite/5.3.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/vite/5.3.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/vite/5.3.2/5.3.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vite/5.3.2/5.3.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

### Release Notes

<details>
<summary>aws/aws-sdk-js-v3 (@&#8203;aws-sdk/client-secrets-manager)</summary>

### [`v3.609.0`](https://github.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-secrets-manager/CHANGELOG.md#36090-2024-07-02)

[Compare Source](https://github.com/aws/aws-sdk-js-v3/compare/v3.606.0...v3.609.0)

**Note:** Version bump only for package [@&#8203;aws-sdk/client-secrets-manager](https://github.com/aws-sdk/client-secrets-manager)

</details>

<details>
<summary>middyjs/middy (@&#8203;middy/core)</summary>

### [`v5.4.3`](https://github.com/middyjs/middy/releases/tag/5.4.3)

[Compare Source](https://github.com/middyjs/middy/compare/5.4.2...5.4.3)

##### What's Changed

-   refactor(ws-response): mutability on response by [@&#8203;nbusser](https://github.com/nbusser) in [https://github.com/middyjs/middy/pull/1220](https://github.com/middyjs/middy/pull/1220)
-   deprecate use of `ava`, `swc`, `c8`, `lerna`, and more

##### New Contributors

-   [@&#8203;nbusser](https://github.com/nbusser) made their first contribution in [https://github.com/middyjs/middy/pull/1220](https://github.com/middyjs/middy/pull/1220)

**Full Changelog**: https://github.com/middyjs/middy/compare/5.4.2...5.4.3

</details>

<details>
<summary>mui/material-ui (@&#8203;mui/icons-material)</summary>

### [`v5.16.0`](https://github.com/mui/material-ui/releases/tag/v5.16.0)

[Compare Source](https://github.com/mui/material-ui/compare/v5.15.21...v5.16.0)

A big thanks to the 5 contributors who made this release possible. Here are some highlights ✨:

-   🚀 Added `InitColorSchemeScript` for Next.js App Router ([#&#8203;42829](https://github.com/mui/material-ui/issues/42829)) [@&#8203;siriwatknp](https://github.com/siriwatknp)

##### `@mui/material@5.16.0`

-   \[Alert] Add ability to override slot props ([@&#8203;alexey-kozlenkov](https://github.com/alexey-kozlenkov)) ([#&#8203;42808](https://github.com/mui/material-ui/issues/42808)) [@&#8203;alexey-kozlenkov](https://github.com/alexey-kozlenkov)
-   Add `InitColorSchemeScript` for Next.js App Router ([#&#8203;42829](https://github.com/mui/material-ui/issues/42829)) [@&#8203;siriwatknp](https://github.com/siriwatknp)
-   Add `DefaultPropsProvider` ([#&#8203;42820](https://github.com/mui/material-ui/issues/42820)) [@&#8203;siriwatknp](https://github.com/siriwatknp)
-   Support `CssVarsTheme` in `responsiveFontSizes` return type ([@&#8203;jxdp](https://github.com/jxdp)) ([#&#8203;42806](https://github.com/mui/material-ui/issues/42806)) [@&#8203;jxdp](https://github.com/jxdp)
-   Remove warning from `getInitColorSchemeScript` ([#&#8203;42838](https://github.com/mui/material-ui/issues/42838)) [@&#8203;siriwatknp](https://github.com/siriwatknp)

##### Docs

-   \[docs] Fix 301 MDN redirections [@&#8203;oliviertassinari](https://github.com/oliviertassinari)

##### Core

-   \[mui-utils]\[test] Remove usages of deprecated react-dom APIs ([@&#8203;aarongarciah](https://github.com/aarongarciah)) ([#&#8203;42813](https://github.com/mui/material-ui/issues/42813)) [@&#8203;aarongarciah](https://github.com/aarongarciah)

All contributors of this release in alphabetical order: [@&#8203;aarongarciah](https://github.com/aarongarciah), [@&#8203;alexey-kozlenkov](https://github.com/alexey-kozlenkov), [@&#8203;jxdp](https://github.com/jxdp), [@&#8203;oliviertassinari](https://github.com/oliviertassinari), [@&#8203;siriwatknp](https://github.com/siriwatknp)

</details>

<details>
<summary>mui/mui-x (@&#8203;mui/x-data-grid)</summary>

### [`v7.9.0`](https://github.com/mui/mui-x/blob/HEAD/CHANGELOG.md#790)

[Compare Source](https://github.com/mui/mui-x/compare/v7.8.0...v7.9.0)

*Jul 5, 2024*

We'd like to offer a big thanks to the 7 contributors who made this release possible. Here are some highlights ✨:

-   🔄 Add loading overlay variants, including a skeleton loader option to the Data Grid component. See [Loading overlay docs](https://mui.com/x/react-data-grid/overlays/#loading-overlay) for more details.
-   🌳 Add `selectItem` and `getItemDOMElement` methods to the TreeView component public API
-   ⛏️ Make the `usePickersTranslations` hook public in the pickers component
-   🐞 Bugfixes



##### Data Grid

##### `@mui/x-data-grid@7.9.0`

-   \[DataGrid] Add skeleton loading overlay support ([#&#8203;13293](https://github.com/mui/mui-x/issues/13293)) [@&#8203;KenanYusuf](https://github.com/KenanYusuf)
-   \[DataGrid] Fix pagination when `pagination={undefined}` ([#&#8203;13349](https://github.com/mui/mui-x/issues/13349)) [@&#8203;sai6855](https://github.com/sai6855)

##### `@mui/x-data-grid-pro@7.9.0` [![pro](https://mui.com/r/x-pro-svg)](https://mui.com/r/x-pro-svg-link "Pro plan")

Same changes as in `@mui/x-data-grid@7.9.0`.

##### `@mui/x-data-grid-premium@7.9.0` [![premium](https://mui.com/r/x-premium-svg)](https://mui.com/r/x-premium-svg-link "Premium plan")

Same changes as in `@mui/x-data-grid-pro@7.9.0`.

##### Date and Time Pickers

##### `@mui/x-date-pickers@7.9.0`

-   \[pickers] Make the `usePickersTranslations` hook public ([#&#8203;13657](https://github.com/mui/mui-x/issues/13657)) [@&#8203;flaviendelangle](https://github.com/flaviendelangle)

##### `@mui/x-date-pickers-pro@7.9.0` [![pro](https://mui.com/r/x-pro-svg)](https://mui.com/r/x-pro-svg-link "Pro plan")

Same changes as in `@mui/x-date-pickers@7.9.0`.

##### Charts

##### `@mui/x-charts@7.9.0`

-   \[charts] Add Heatmap (unreleased) ([#&#8203;13209](https://github.com/mui/mui-x/issues/13209)) [@&#8203;alexfauquette](https://github.com/alexfauquette)
-   \[charts] Add initial `Zoom&Pan` to the Pro charts (unreleased) ([#&#8203;13405](https://github.com/mui/mui-x/issues/13405)) [@&#8203;JCQuintas](https://github.com/JCQuintas)
-   \[charts] Fix Axis Highlight on horizontal bar charts regression ([#&#8203;13717](https://github.com/mui/mui-x/issues/13717)) [@&#8203;JCQuintas](https://github.com/JCQuintas)
-   \[charts] Improve charts interaction for mobile users ([#&#8203;13692](https://github.com/mui/mui-x/issues/13692)) [@&#8203;JCQuintas](https://github.com/JCQuintas)
-   \[charts] Add documentation on how to disable the tooltip on charts ([#&#8203;13724](https://github.com/mui/mui-x/issues/13724)) [@&#8203;JCQuintas](https://github.com/JCQuintas)

##### Tree View

##### `@mui/x-tree-view@7.9.0`

-   \[TreeView] Add `selectItem` and `getItemDOMElement` methods to the public API ([#&#8203;13485](https://github.com/mui/mui-x/issues/13485)) [@&#8203;flaviendelangle](https://github.com/flaviendelangle)

##### Docs

-   \[docs] Fix custom "no results overlay" demo in dark mode ([#&#8203;13715](https://github.com/mui/mui-x/issues/13715)) [@&#8203;KenanYusuf](https://github.com/KenanYusuf)

##### Core

-   \[core] Add `react_next` workflow in CircleCI ([#&#8203;13360](https://github.com/mui/mui-x/issues/13360)) [@&#8203;cherniavskii](https://github.com/cherniavskii)
-   \[core] Create a new package to share utils across X packages ([#&#8203;13528](https://github.com/mui/mui-x/issues/13528)) [@&#8203;flaviendelangle](https://github.com/flaviendelangle)
-   \[core] Fix dependency setup ([#&#8203;13684](https://github.com/mui/mui-x/issues/13684)) [@&#8203;LukasTy](https://github.com/LukasTy)
-   \[core] Remove `jscodeshift-add-imports` package ([#&#8203;13720](https://github.com/mui/mui-x/issues/13720)) [@&#8203;LukasTy](https://github.com/LukasTy)
-   \[code-infra] Cleanup monorepo and `@mui/docs` usage ([#&#8203;13713](https://github.com/mui/mui-x/issues/13713)) [@&#8203;LukasTy](https://github.com/LukasTy)

</details>

<details>
<summary>trautonen/cdk-dns-validated-certificate (@&#8203;trautonen/cdk-dns-validated-certificate)</summary>

### [`v0.1.4`](https://github.com/trautonen/cdk-dns-validated-certificate/releases/tag/v0.1.4)

[Compare Source](https://github.com/trautonen/cdk-dns-validated-certificate/compare/v0.1.3...v0.1.4)

##### [0.1.4](https://github.com/trautonen/cdk-dns-validated-certificate/compare/v0.1.3...v0.1.4) (2024-07-02)

</details>

<details>
<summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/eslint-plugin)</summary>

### [`v7.15.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#7150-2024-07-01)

[Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v7.14.1...v7.15.0)

##### 🚀 Features

-   **eslint-plugin:** \[array-type] detect `Readonly<string[]>` case

-   **eslint-plugin:** back-port new rules around empty object types from v8

##### 🩹 Fixes

-   disable `EXPERIMENTAL_useProjectService` in `disabled-type-checked` shared config

-   **eslint-plugin:** \[no-unsafe-return] differentiate a types-error any from a true any

-   **eslint-plugin:** \[no-unsafe-call] differentiate a types-error any from a true any

##### ❤️  Thank You

-   auvred
-   Kim Sang Du
-   rgehbt
-   Vinccool96

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

</details>

<details>
<summary>aws/aws-cdk (aws-cdk)</summary>

### [`v2.148.0`](https://github.com/aws/aws-cdk/releases/tag/v2.148.0)

[Compare Source](https://github.com/aws/aws-cdk/compare/v2.147.3...v2.148.0)

##### Features

-   **lambda:** add grantInvokeLatestVersion to grant invoke only to latest function version ([#&#8203;29856](https://github.com/aws/aws-cdk/issues/29856)) ([61c28dd](https://github.com/aws/aws-cdk/commit/61c28dd79603ae50865f8b7a7f535ba4f7f69500)), closes [#&#8203;20177](https://github.com/aws/aws-cdk/issues/20177)
-   update L1 CloudFormation resource definitions ([#&#8203;30722](https://github.com/aws/aws-cdk/issues/30722)) ([4ceeced](https://github.com/aws/aws-cdk/commit/4ceecedd3d91465b29db21b10239937b99b5f79c)), closes [/docs.aws.amazon.com/service-terms/#&#8203;87](https://github.com/aws//docs.aws.amazon.com/service-terms//issues/87)
-   **codebuild:** adding `project.visibility` ([#&#8203;30103](https://github.com/aws/aws-cdk/issues/30103)) ([1bacb69](https://github.com/aws/aws-cdk/commit/1bacb69b6976dd75da78b45b07d6fec9306a6d72))
-   **codedeploy:** termination hook ([#&#8203;30644](https://github.com/aws/aws-cdk/issues/30644)) ([8f652a7](https://github.com/aws/aws-cdk/commit/8f652a7f9090502f70d2c733dd8a87619663ceb8))
-   **cognito:** add defaultRedirectUri to UserPoolClient ([#&#8203;30481](https://github.com/aws/aws-cdk/issues/30481)) ([f2c5f68](https://github.com/aws/aws-cdk/commit/f2c5f68b04e0cf89a7dcd453448988ba727c3363))
-   **eks:** eks pod identities ([#&#8203;30576](https://github.com/aws/aws-cdk/issues/30576)) ([9437b4d](https://github.com/aws/aws-cdk/commit/9437b4dbbea15db18ff2991d410e033cc3437001)), closes [/github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-eks/lib/oidc-provider.ts#L36](https://github.com/aws//github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-eks/lib/oidc-provider.ts/issues/L36) [/github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-eks/lib/oidc-provider.ts#L36](https://github.com/aws//github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-eks/lib/oidc-provider.ts/issues/L36) [/github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-iam/lib/role.ts#L373](https://github.com/aws//github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-iam/lib/role.ts/issues/L373) [#&#8203;30519](https://github.com/aws/aws-cdk/issues/30519)
-   **stepfunctions-tasks:** step functions task for cross-region AWS API call ([#&#8203;30061](https://github.com/aws/aws-cdk/issues/30061)) ([1397737](https://github.com/aws/aws-cdk/commit/1397737e16066d9101fd1c2fc85cd8396d738869)), closes [#&#8203;29918](https://github.com/aws/aws-cdk/issues/29918)
-   update L1 CloudFormation resource definitions ([#&#8203;30642](https://github.com/aws/aws-cdk/issues/30642)) ([2a659f0](https://github.com/aws/aws-cdk/commit/2a659f0ebbc039a03402b7f99a36dbf461e026aa))
-   **fsx:** add properties to enable automatic backups  for Lustre file system ([#&#8203;30343](https://github.com/aws/aws-cdk/issues/30343)) ([3b95777](https://github.com/aws/aws-cdk/commit/3b95777ee5dae32fd41481d81922d07c804a2c6b)), closes [#&#8203;30340](https://github.com/aws/aws-cdk/issues/30340)

##### Bug Fixes

-   **ecs:** let AsgCapacityProvider use IAutoScalingGroup only when Managed Termination Protection is disable ([#&#8203;30335](https://github.com/aws/aws-cdk/issues/30335)) ([efee07d](https://github.com/aws/aws-cdk/commit/efee07d6f17356b52b2a2e120ebe0404f554188b)), closes [#&#8203;29174](https://github.com/aws/aws-cdk/issues/29174)
-   **lambda-nodejs:** breaking change in esbuild causes import module error ([#&#8203;30726](https://github.com/aws/aws-cdk/issues/30726)) ([7f5ce4b](https://github.com/aws/aws-cdk/commit/7f5ce4bfe94b19efe6c0c8aa0ec850cdfc4b8ebb)), closes [#&#8203;30717](https://github.com/aws/aws-cdk/issues/30717)
-   **s3:** allow import S3 bucket with a legacy name ([#&#8203;30679](https://github.com/aws/aws-cdk/issues/30679)) ([e09126f](https://github.com/aws/aws-cdk/commit/e09126f6d97a52ee39811f8cbf874b722928debc)), closes [#&#8203;22640](https://github.com/aws/aws-cdk/issues/22640)
-   **s3-notifications:** unable to delete the existing S3 event notifications ([#&#8203;30610](https://github.com/aws/aws-cdk/issues/30610)) ([b880067](https://github.com/aws/aws-cdk/commit/b8800675d638bd866dc2444af895a650aea12ca7)), closes [#&#8203;28915](https://github.com/aws/aws-cdk/issues/28915)s too broad (under feature flag) ([#&#8203;30389](https://github.com/aws/aws-cdk/issues/30389)) ([8ebfade](https://github.com/aws/aws-cdk/commit/8ebfadeb8d7a8c15176ed9e5f106a49fc84040a6)), closes [#&#8203;30368](https://github.com/aws/aws-cdk/issues/30368)

##### Reverts

-   fix(core): overrideLogicalId validation ([#&#8203;30695](https://github.com/aws/aws-cdk/issues/30695)) ([0aa2be7](https://github.com/aws/aws-cdk/commit/0aa2be754ad667d40791557f0a8707b4ab6e6d4c)), closes [aws/aws-cdk#29708](https://github.com/aws/aws-cdk/issues/29708)
-   route53 CrossAccountZoneDelegationRecord fails at deployment time with imported `delegatedZone` ([#&#8203;30440](https://github.com/aws/aws-cdk/issues/30440))" ([#&#8203;30606](https://github.com/aws/aws-cdk/issues/30606)) ([95280a0](https://github.com/aws/aws-cdk/commit/95280a080a6e5a6f02932c80c092c8b7dac8ded8)), closes [#&#8203;30600](https://github.com/aws/aws-cdk/issues/30600)

***

##### Alpha modules (2.148.0-alpha.0)

##### Features

-   **apprunner:** add AutoScalingConfiguration for AppRunner Service ([#&#8203;30358](https://github.com/aws/aws-cdk/issues/30358)) ([a598508](https://github.com/aws/aws-cdk/commit/a598508e2a86c5932cbbbc4249cdc228bf2cbf39)), closes [#&#8203;30353](https://github.com/aws/aws-cdk/issues/30353)
-   **apprunner:** add ObservabilityConfiguration for AppRunner Service ([#&#8203;30359](https://github.com/aws/aws-cdk/issues/30359)) ([9e9cc27](https://github.com/aws/aws-cdk/commit/9e9cc277d55774b0b2e8887676ddb328eb662d74)), closes [#&#8203;22985](https://github.com/aws/aws-cdk/issues/22985)
-   **pipes-enrichments:** add Step Functions enrichment eventbridge pipes ([#&#8203;30495](https://github.com/aws/aws-cdk/issues/30495)) ([8b495f9](https://github.com/aws/aws-cdk/commit/8b495f9ec157c0b00674715f62b1bbcabf2096ac)), closes [#&#8203;29385](https://github.com/aws/aws-cdk/issues/29385)
-   **pipes-targets:** add lambda function ([#&#8203;30271](https://github.com/aws/aws-cdk/issues/30271)) ([f594fae](https://github.com/aws/aws-cdk/commit/f594fae922ea19c087c56405046098e5683d2c70)), closes [#&#8203;30270](https://github.com/aws/aws-cdk/issues/30270)

##### Bug Fixes

-   **apprunner:** auto deployment fails after new container image  pushed due to lack of a permission ([#&#8203;30630](https://github.com/aws/aws-cdk/issues/30630)) ([cce10b1](https://github.com/aws/aws-cdk/commit/cce10b1c1f0f764e39e734ad7d6c288b7ffb9da3)), closes [#&#8203;26640](https://github.com/aws/aws-cdk/issues/26640) [/github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-ecr/lib/repository.ts#L385](https://github.com/aws//github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-ecr/lib/repository.ts/issues/L385) [40aws-cdk/aws-apprunner-alpha/lib/service.ts#L1303](https://github.com/40aws-cdk/aws-apprunner-alpha/lib/service.ts/issues/L1303) [40aws-cdk/aws-apprunner-alpha/lib/service.ts#L1368](https://github.com/40aws-cdk/aws-apprunner-alpha/lib/service.ts/issues/L1368)

### [`v2.147.3`](https://github.com/aws/aws-cdk/releases/tag/v2.147.3)

[Compare Source](https://github.com/aws/aws-cdk/compare/v2.147.2...v2.147.3)

##### Bug Fixes

-   **lambda-nodejs:** breaking change in esbuild causes import module error ([#&#8203;30726](https://github.com/aws/aws-cdk/issues/30726)) ([06c14b1](https://github.com/aws/aws-cdk/commit/06c14b16d04353e9e108b58edc1450d018c24b12)), closes [#&#8203;30717](https://github.com/aws/aws-cdk/issues/30717)

***

#### Alpha modules (2.147.3-alpha.0)

</details>

<details>
<summary>evanw/esbuild (esbuild)</summary>

### [`v0.23.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230)

[Compare Source](https://github.com/evanw/esbuild/compare/v0.22.0...v0.23.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.22.0` or `~0.22.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information.

-   Revert the recent change to avoid bundling dependencies for node ([#&#8203;3819](https://github.com/evanw/esbuild/issues/3819))

    This release reverts the recent change in version 0.22.0 that made `--packages=external` the default behavior with `--platform=node`.  The default is now back to `--packages=bundle`.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

-   Fix preserving collapsed JSX whitespace ([#&#8203;3818](https://github.com/evanw/esbuild/issues/3818))

    When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is an example:

    ```jsx
    // Original code
    <Foo>
      <Bar />
    </Foo>

    // Old output (with --jsx=preserve)
    <Foo><Bar /></Foo>;

    // New output (with --jsx=preserve)
    <Foo>
      <Bar />
    </Foo>;
    ```

### [`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information.

-   Omit packages from bundles by default when targeting node ([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874), [#&#8203;2830](https://github.com/evanw/esbuild/issues/2830), [#&#8203;2846](https://github.com/evanw/esbuild/issues/2846), [#&#8203;2915](https://github.com/evanw/esbuild/issues/2915), [#&#8203;3145](https://github.com/evanw/esbuild/issues/3145), [#&#8203;3294](https://github.com/evanw/esbuild/issues/3294), [#&#8203;3323](https://github.com/evanw/esbuild/issues/3323), [#&#8203;3582](https://github.com/evanw/esbuild/issues/3582), [#&#8203;3809](https://github.com/evanw/esbuild/issues/3809), [#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for `--platform=node`) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use `--packages=external` to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is `node` (i.e. the previous behavior of `--packages=external` is now the default in this case). *Note that your dependencies must now be present on the file system when your bundle is run.* If you don't want this behavior, you can do `--packages=bundle` to allow packages to be included in the bundle (i.e. the previous default behavior). Note that `--packages=bundle` doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using `--external:` even when `--packages=bundle` is present.

    The `--packages=` setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of `/` or `.` or `..` are considered to be package imports. The only two exceptions to this rule are [subpath imports](https://nodejs.org/api/packages.html#subpath-imports) (which start with a `#` character) and TypeScript path remappings via `paths` and/or `baseUrl` in `tsconfig.json` (which are applied first).

-   Drop support for older platforms ([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

    This is because the Go programming language dropped support for these operating system versions in [Go 1.21](https://go.dev/doc/go1.21#windows), and this release updates esbuild from Go 1.20 to Go 1.22.

    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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

    In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's [release schedule](https://nodejs.org/en/about/previous-releases) for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the `esbuild-wasm` package and versions of node before node 17.4 (specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

    TypeScript 5.5 subtly changes the way `await using` behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in [microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

    The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: <https://2ality.com/2024/06/ecmascript-2024.html>. The only addition that's relevant for esbuild is the regular expression `/v` flag. With `--target=es2024`, regular expressions that use the `/v` flag will now be passed through untransformed instead of being transformed into a call to `new RegExp`.

-   Publish binaries for OpenBSD on 64-bit ARM ([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665), [#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

    With this release, you should now be able to install the `esbuild` npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

    This was contributed by [@&#8203;ikmckenz](https://github.com/ikmckenz).

-   Publish binaries for WASI (WebAssembly System Interface) preview 1 ([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300), [#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

    The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a `.wasm` file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).

    Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has [released support for preview 1](https://go.dev/blog/wasi), which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.

    This release publishes esbuild precompiled for WASI preview 1 to the `@esbuild/wasi-preview1` package on npm (specifically the file `@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.

-   Warn about `onResolve` plugins not setting a path ([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

    Plugins that return values from `onResolve` without resolving the path (i.e. without setting either `path` or `external: true`) will now cause a warning. This is because esbuild only uses return values from `onResolve` if it successfully resolves the path, and it's not good for invalid input to be silently ignored.

-   Add a new Go API for running the CLI with plugins ([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

    With esbuild's Go API, you can now call `cli.RunWithPlugins(args, plugins)` to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.

    This was contributed by [@&#8203;edewit](https://github.com/edewit).

</details>

<details>
<summary>Microsoft/TypeScript (typescript)</summary>

### [`v5.5.3`](https://github.com/Microsoft/TypeScript/compare/v5.5.2...f0e992167440686f948965e5441a918b34251886)

[Compare Source](https://github.com/Microsoft/TypeScript/compare/v5.5.2...v5.5.3)

</details>

<details>
<summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/parser)</summary>

### [`v7.15.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#7150-2024-07-01)

[Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v7.14.1...v7.15.0)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

</details>

<details>
<summary>remix-run/react-router (react-router)</summary>

### [`v6.24.1`](https://github.com/remix-run/react-router/blob/HEAD/packages/react-router/CHANGELOG.md#6241)

[Compare Source](https://github.com/remix-run/react-router/compare/react-router@6.24.0...react-router@6.24.1)

##### Patch Changes

-   When using `future.v7_relativeSplatPath`, properly resolve relative paths in splat routes that are children of pathless routes ([#&#8203;11633](https://github.com/remix-run/react-router/pull/11633))
-   Updated dependencies:
    -   `@remix-run/router@1.17.1`

</details>

<details>
<summary>remix-run/react-router (react-router-dom)</summary>

### [`v6.24.1`](https://github.com/remix-run/react-router/blob/HEAD/packages/react-router-dom/CHANGELOG.md#6241)

[Compare Source](https://github.com/remix-run/react-router/compare/react-router-dom@6.24.0...react-router-dom@6.24.1)

##### Patch Changes

-   Remove `polyfill.io` reference from warning message because the domain was sold and has since been determined to serve malware ([#&#8203;11741](https://github.com/remix-run/react-router/pull/11741))
    -   See <https://sansec.io/research/polyfill-supply-chain-attack>
-   Export `NavLinkRenderProps` type for easier typing of custom `NavLink` callback ([#&#8203;11553](https://github.com/remix-run/react-router/pull/11553))
-   Updated dependencies:
    -   `@remix-run/router@1.17.1`
    -   `react-router@6.24.1`

</details>

<details>
<summary>vitejs/vite (vite)</summary>

### [`v5.3.3`](https://github.com/vitejs/vite/blob/HEAD/packages/vite/CHANGELOG.md#small533-2024-07-03-small)

[Compare Source](https://github.com/vitejs/vite/compare/v5.3.2...v5.3.3)

-   fix: lazily evaluate \__vite\_\_mapDeps files ([#&#8203;17602](https://github.com/vitejs/vite/issues/17602)) ([dafff4a](https://github.com/vitejs/vite/commit/dafff4a)), closes [#&#8203;17602](https://github.com/vitejs/vite/issues/17602)
-   fix(deps): update all non-major dependencies ([#&#8203;17590](https://github.com/vitejs/vite/issues/17590)) ([012490c](https://github.com/vitejs/vite/commit/012490c)), closes [#&#8203;17590](https://github.com/vitejs/vite/issues/17590)
-   fix(lib): remove pure CSS dynamic import ([#&#8203;17601](https://github.com/vitejs/vite/issues/17601)) ([055f1c1](https://github.com/vitejs/vite/commit/055f1c1)), closes [#&#8203;17601](https://github.com/vitejs/vite/issues/17601)
-   fix(proxy): replace changeOrigin changes in 5.3.0 with new rewriteWsOrigin option ([#&#8203;17563](https://github.com/vitejs/vite/issues/17563)) ([14c3d49](https://github.com/vitejs/vite/commit/14c3d49)), closes [#&#8203;17563](https://github.com/vitejs/vite/issues/17563)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 6am on saturday" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/SvenKirschbaum/aws-utils).
mergify bot pushed a commit to SvenKirschbaum/share.kirschbaum.cloud that referenced this pull request Jul 6, 2024
[![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Type | Update | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|---|---|
|  |  | lockFileMaintenance | All locks refreshed |  |  |  |  |
| [@aws-sdk/client-dynamodb](https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-dynamodb) ([source](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-dynamodb)) | dependencies | minor | [`3.606.0` -> `3.609.0`](https://renovatebot.com/diffs/npm/@aws-sdk%2fclient-dynamodb/3.606.0/3.609.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@aws-sdk%2fclient-dynamodb/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@aws-sdk%2fclient-dynamodb/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@aws-sdk%2fclient-dynamodb/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@aws-sdk%2fclient-dynamodb/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@aws-sdk/client-s3](https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-s3) ([source](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-s3)) | dependencies | minor | [`3.606.0` -> `3.609.0`](https://renovatebot.com/diffs/npm/@aws-sdk%2fclient-s3/3.606.0/3.609.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@aws-sdk%2fclient-s3/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@aws-sdk%2fclient-s3/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@aws-sdk%2fclient-s3/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@aws-sdk%2fclient-s3/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@aws-sdk/client-sesv2](https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-sesv2) ([source](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-sesv2)) | dependencies | minor | [`3.606.0` -> `3.609.0`](https://renovatebot.com/diffs/npm/@aws-sdk%2fclient-sesv2/3.606.0/3.609.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@aws-sdk%2fclient-sesv2/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@aws-sdk%2fclient-sesv2/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@aws-sdk%2fclient-sesv2/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@aws-sdk%2fclient-sesv2/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@aws-sdk/client-sfn](https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-sfn) ([source](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/clients/client-sfn)) | dependencies | minor | [`3.606.0` -> `3.609.0`](https://renovatebot.com/diffs/npm/@aws-sdk%2fclient-sfn/3.606.0/3.609.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@aws-sdk%2fclient-sfn/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@aws-sdk%2fclient-sfn/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@aws-sdk%2fclient-sfn/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@aws-sdk%2fclient-sfn/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@aws-sdk/s3-request-presigner](https://github.com/aws/aws-sdk-js-v3/tree/main/packages/s3-request-presigner) ([source](https://github.com/aws/aws-sdk-js-v3/tree/HEAD/packages/s3-request-presigner)) | dependencies | minor | [`3.606.0` -> `3.609.0`](https://renovatebot.com/diffs/npm/@aws-sdk%2fs3-request-presigner/3.606.0/3.609.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@aws-sdk%2fs3-request-presigner/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@aws-sdk%2fs3-request-presigner/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@aws-sdk%2fs3-request-presigner/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@aws-sdk%2fs3-request-presigner/3.606.0/3.609.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/core](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/core)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fcore/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fcore/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fcore/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fcore/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fcore/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/error-logger](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/error-logger)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2ferror-logger/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2ferror-logger/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2ferror-logger/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2ferror-logger/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2ferror-logger/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-content-negotiation](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-content-negotiation)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-content-negotiation/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-content-negotiation/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-content-negotiation/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-content-negotiation/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-content-negotiation/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-error-handler](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-error-handler)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-error-handler/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-error-handler/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-error-handler/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-error-handler/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-error-handler/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-header-normalizer](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-header-normalizer)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-header-normalizer/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-header-normalizer/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-header-normalizer/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-header-normalizer/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-header-normalizer/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-json-body-parser](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-json-body-parser)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-json-body-parser/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-json-body-parser/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-json-body-parser/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-json-body-parser/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-json-body-parser/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/http-response-serializer](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/http-response-serializer)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fhttp-response-serializer/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fhttp-response-serializer/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fhttp-response-serializer/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fhttp-response-serializer/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fhttp-response-serializer/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@middy/validator](https://middy.js.org) ([source](https://github.com/middyjs/middy/tree/HEAD/packages/validator)) | dependencies | patch | [`5.4.2` -> `5.4.3`](https://renovatebot.com/diffs/npm/@middy%2fvalidator/5.4.2/5.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@middy%2fvalidator/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@middy%2fvalidator/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@middy%2fvalidator/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@middy%2fvalidator/5.4.2/5.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@mui/icons-material](https://mui.com/material-ui/material-icons/) ([source](https://github.com/mui/material-ui/tree/HEAD/packages/mui-icons-material)) | dependencies | minor | [`5.15.21` -> `5.16.0`](https://renovatebot.com/diffs/npm/@mui%2ficons-material/5.15.21/5.16.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@mui%2ficons-material/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@mui%2ficons-material/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@mui%2ficons-material/5.15.21/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@mui%2ficons-material/5.15.21/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@mui/material](https://mui.com/material-ui/) ([source](https://github.com/mui/material-ui/tree/HEAD/packages/mui-material)) | dependencies | minor | [`5.15.21` -> `5.16.0`](https://renovatebot.com/diffs/npm/@mui%2fmaterial/5.15.21/5.16.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@mui%2fmaterial/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@mui%2fmaterial/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@mui%2fmaterial/5.15.21/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@mui%2fmaterial/5.15.21/5.16.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@mui/x-date-pickers](https://mui.com/x/react-date-pickers/) ([source](https://github.com/mui/mui-x/tree/HEAD/packages/x-date-pickers)) | dependencies | minor | [`7.8.0` -> `7.9.0`](https://renovatebot.com/diffs/npm/@mui%2fx-date-pickers/7.8.0/7.9.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@mui%2fx-date-pickers/7.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@mui%2fx-date-pickers/7.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@mui%2fx-date-pickers/7.8.0/7.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@mui%2fx-date-pickers/7.8.0/7.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@trautonen/cdk-dns-validated-certificate](https://github.com/trautonen/cdk-dns-validated-certificate) | dependencies | patch | [`0.1.3` -> `0.1.4`](https://renovatebot.com/diffs/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.3/0.1.4) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.3/0.1.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@trautonen%2fcdk-dns-validated-certificate/0.1.3/0.1.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/node) ([source](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)) | devDependencies | patch | [`20.14.9` -> `20.14.10`](https://renovatebot.com/diffs/npm/@types%2fnode/20.14.9/20.14.10) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@types%2fnode/20.14.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@types%2fnode/20.14.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@types%2fnode/20.14.9/20.14.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@types%2fnode/20.14.9/20.14.10?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@typescript-eslint/eslint-plugin](https://typescript-eslint.io/packages/eslint-plugin) ([source](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin)) | devDependencies | minor | [`7.14.1` -> `7.15.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2feslint-plugin/7.14.1/7.15.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@typescript-eslint%2feslint-plugin/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@typescript-eslint%2feslint-plugin/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@typescript-eslint%2feslint-plugin/7.14.1/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@typescript-eslint%2feslint-plugin/7.14.1/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [@typescript-eslint/parser](https://typescript-eslint.io/packages/parser) ([source](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser)) | devDependencies | minor | [`7.14.1` -> `7.15.0`](https://renovatebot.com/diffs/npm/@typescript-eslint%2fparser/7.14.1/7.15.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@typescript-eslint%2fparser/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@typescript-eslint%2fparser/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@typescript-eslint%2fparser/7.14.1/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@typescript-eslint%2fparser/7.14.1/7.15.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [aws-cdk](https://github.com/aws/aws-cdk) ([source](https://github.com/aws/aws-cdk/tree/HEAD/packages/aws-cdk)) | devDependencies | minor | [`2.147.2` -> `2.148.0`](https://renovatebot.com/diffs/npm/aws-cdk/2.147.2/2.148.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/aws-cdk/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/aws-cdk/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/aws-cdk/2.147.2/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/aws-cdk/2.147.2/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [aws-cdk-lib](https://github.com/aws/aws-cdk) ([source](https://github.com/aws/aws-cdk/tree/HEAD/packages/aws-cdk-lib)) | dependencies | minor | [`2.147.2` -> `2.148.0`](https://renovatebot.com/diffs/npm/aws-cdk-lib/2.147.2/2.148.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/aws-cdk-lib/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/aws-cdk-lib/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/aws-cdk-lib/2.147.2/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/aws-cdk-lib/2.147.2/2.148.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [aws-sdk](https://github.com/aws/aws-sdk-js) | dependencies | minor | [`2.1651.0` -> `2.1655.0`](https://renovatebot.com/diffs/npm/aws-sdk/2.1651.0/2.1655.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/aws-sdk/2.1655.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/aws-sdk/2.1655.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/aws-sdk/2.1651.0/2.1655.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/aws-sdk/2.1651.0/2.1655.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [esbuild](https://github.com/evanw/esbuild) | dependencies | minor | [`0.21.5` -> `0.23.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.5/0.23.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [glob](https://github.com/isaacs/node-glob) | devDependencies | patch | [`10.4.2` -> `10.4.3`](https://renovatebot.com/diffs/npm/glob/10.4.2/10.4.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/glob/10.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/glob/10.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/glob/10.4.2/10.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/glob/10.4.2/10.4.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [react-router](https://github.com/remix-run/react-router) ([source](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router)) | dependencies | patch | [`6.24.0` -> `6.24.1`](https://renovatebot.com/diffs/npm/react-router/6.24.0/6.24.1) | [![age](https://developer.mend.io/api/mc/badges/age/npm/react-router/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/react-router/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/react-router/6.24.0/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/react-router/6.24.0/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [typescript](https://www.typescriptlang.org/) ([source](https://github.com/Microsoft/TypeScript)) | devDependencies | patch | [`5.5.2` -> `5.5.3`](https://renovatebot.com/diffs/npm/typescript/5.5.2/5.5.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/typescript/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/typescript/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/typescript/5.5.2/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/typescript/5.5.2/5.5.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [react-router-dom](https://github.com/remix-run/react-router) ([source](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom)) | dependencies | patch | [`6.24.0` -> `6.24.1`](https://renovatebot.com/diffs/npm/react-router-dom/6.24.0/6.24.1) | [![age](https://developer.mend.io/api/mc/badges/age/npm/react-router-dom/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/react-router-dom/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/react-router-dom/6.24.0/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/react-router-dom/6.24.0/6.24.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [vite](https://vitejs.dev) ([source](https://github.com/vitejs/vite/tree/HEAD/packages/vite)) | devDependencies | patch | [`5.3.2` -> `5.3.3`](https://renovatebot.com/diffs/npm/vite/5.3.2/5.3.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/vite/5.3.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/vite/5.3.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/vite/5.3.2/5.3.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vite/5.3.2/5.3.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) |
| [web-vitals](https://github.com/GoogleChrome/web-vitals) | dependencies | patch | [`4.2.0` -> `4.2.1`](https://renovatebot.com/diffs/npm/web-vitals/4.2.0/4.2.1) | [![age](https://developer.mend.io/api/mc/badges/age/npm/web-vitals/4.2.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/web-vitals/4.2.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/web-vitals/4.2.0/4.2.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/web-vitals/4.2.0/4.2.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) |

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

### Release Notes

<details>
<summary>aws/aws-sdk-js-v3 (@&#8203;aws-sdk/client-dynamodb)</summary>

### [`v3.609.0`](https://github.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-dynamodb/CHANGELOG.md#36090-2024-07-02)

[Compare Source](https://github.com/aws/aws-sdk-js-v3/compare/v3.606.0...v3.609.0)

**Note:** Version bump only for package [@&#8203;aws-sdk/client-dynamodb](https://github.com/aws-sdk/client-dynamodb)

</details>

<details>
<summary>aws/aws-sdk-js-v3 (@&#8203;aws-sdk/client-s3)</summary>

### [`v3.609.0`](https://github.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-s3/CHANGELOG.md#36090-2024-07-02)

[Compare Source](https://github.com/aws/aws-sdk-js-v3/compare/v3.608.0...v3.609.0)

##### Features

-   **client-s3:** Added response overrides to Head Object requests. ([ac9f3d2](https://github.com/aws/aws-sdk-js-v3/commit/ac9f3d205f6c848d17b9e7680ccd3f0336e7a378))

### [`v3.608.0`](https://github.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-s3/CHANGELOG.md#36080-2024-07-01)

[Compare Source](https://github.com/aws/aws-sdk-js-v3/compare/v3.606.0...v3.608.0)

**Note:** Version bump only for package [@&#8203;aws-sdk/client-s3](https://github.com/aws-sdk/client-s3)

</details>

<details>
<summary>aws/aws-sdk-js-v3 (@&#8203;aws-sdk/client-sesv2)</summary>

### [`v3.609.0`](https://github.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-sesv2/CHANGELOG.md#36090-2024-07-02)

[Compare Source](https://github.com/aws/aws-sdk-js-v3/compare/v3.608.0...v3.609.0)

**Note:** Version bump only for package [@&#8203;aws-sdk/client-sesv2](https://github.com/aws-sdk/client-sesv2)

### [`v3.608.0`](https://github.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-sesv2/CHANGELOG.md#36080-2024-07-01)

[Compare Source](https://github.com/aws/aws-sdk-js-v3/compare/v3.606.0...v3.608.0)

**Note:** Version bump only for package [@&#8203;aws-sdk/client-sesv2](https://github.com/aws-sdk/client-sesv2)

</details>

<details>
<summary>aws/aws-sdk-js-v3 (@&#8203;aws-sdk/client-sfn)</summary>

### [`v3.609.0`](https://github.com/aws/aws-sdk-js-v3/blob/HEAD/clients/client-sfn/CHANGELOG.md#36090-2024-07-02)

[Compare Source](https://github.com/aws/aws-sdk-js-v3/compare/v3.606.0...v3.609.0)

**Note:** Version bump only for package [@&#8203;aws-sdk/client-sfn](https://github.com/aws-sdk/client-sfn)

</details>

<details>
<summary>aws/aws-sdk-js-v3 (@&#8203;aws-sdk/s3-request-presigner)</summary>

### [`v3.609.0`](https://github.com/aws/aws-sdk-js-v3/blob/HEAD/packages/s3-request-presigner/CHANGELOG.md#36090-2024-07-02)

[Compare Source](https://github.com/aws/aws-sdk-js-v3/compare/v3.608.0...v3.609.0)

**Note:** Version bump only for package [@&#8203;aws-sdk/s3-request-presigner](https://github.com/aws-sdk/s3-request-presigner)

### [`v3.608.0`](https://github.com/aws/aws-sdk-js-v3/blob/HEAD/packages/s3-request-presigner/CHANGELOG.md#36080-2024-07-01)

[Compare Source](https://github.com/aws/aws-sdk-js-v3/compare/v3.606.0...v3.608.0)

**Note:** Version bump only for package [@&#8203;aws-sdk/s3-request-presigner](https://github.com/aws-sdk/s3-request-presigner)

</details>

<details>
<summary>middyjs/middy (@&#8203;middy/core)</summary>

### [`v5.4.3`](https://github.com/middyjs/middy/releases/tag/5.4.3)

[Compare Source](https://github.com/middyjs/middy/compare/5.4.2...5.4.3)

##### What's Changed

-   refactor(ws-response): mutability on response by [@&#8203;nbusser](https://github.com/nbusser) in [https://github.com/middyjs/middy/pull/1220](https://github.com/middyjs/middy/pull/1220)
-   deprecate use of `ava`, `swc`, `c8`, `lerna`, and more

##### New Contributors

-   [@&#8203;nbusser](https://github.com/nbusser) made their first contribution in [https://github.com/middyjs/middy/pull/1220](https://github.com/middyjs/middy/pull/1220)

**Full Changelog**: https://github.com/middyjs/middy/compare/5.4.2...5.4.3

</details>

<details>
<summary>mui/material-ui (@&#8203;mui/icons-material)</summary>

### [`v5.16.0`](https://github.com/mui/material-ui/releases/tag/v5.16.0)

[Compare Source](https://github.com/mui/material-ui/compare/v5.15.21...v5.16.0)

A big thanks to the 5 contributors who made this release possible. Here are some highlights ✨:

-   🚀 Added `InitColorSchemeScript` for Next.js App Router ([#&#8203;42829](https://github.com/mui/material-ui/issues/42829)) [@&#8203;siriwatknp](https://github.com/siriwatknp)

##### `@mui/material@5.16.0`

-   \[Alert] Add ability to override slot props ([@&#8203;alexey-kozlenkov](https://github.com/alexey-kozlenkov)) ([#&#8203;42808](https://github.com/mui/material-ui/issues/42808)) [@&#8203;alexey-kozlenkov](https://github.com/alexey-kozlenkov)
-   Add `InitColorSchemeScript` for Next.js App Router ([#&#8203;42829](https://github.com/mui/material-ui/issues/42829)) [@&#8203;siriwatknp](https://github.com/siriwatknp)
-   Add `DefaultPropsProvider` ([#&#8203;42820](https://github.com/mui/material-ui/issues/42820)) [@&#8203;siriwatknp](https://github.com/siriwatknp)
-   Support `CssVarsTheme` in `responsiveFontSizes` return type ([@&#8203;jxdp](https://github.com/jxdp)) ([#&#8203;42806](https://github.com/mui/material-ui/issues/42806)) [@&#8203;jxdp](https://github.com/jxdp)
-   Remove warning from `getInitColorSchemeScript` ([#&#8203;42838](https://github.com/mui/material-ui/issues/42838)) [@&#8203;siriwatknp](https://github.com/siriwatknp)

##### Docs

-   \[docs] Fix 301 MDN redirections [@&#8203;oliviertassinari](https://github.com/oliviertassinari)

##### Core

-   \[mui-utils]\[test] Remove usages of deprecated react-dom APIs ([@&#8203;aarongarciah](https://github.com/aarongarciah)) ([#&#8203;42813](https://github.com/mui/material-ui/issues/42813)) [@&#8203;aarongarciah](https://github.com/aarongarciah)

All contributors of this release in alphabetical order: [@&#8203;aarongarciah](https://github.com/aarongarciah), [@&#8203;alexey-kozlenkov](https://github.com/alexey-kozlenkov), [@&#8203;jxdp](https://github.com/jxdp), [@&#8203;oliviertassinari](https://github.com/oliviertassinari), [@&#8203;siriwatknp](https://github.com/siriwatknp)

</details>

<details>
<summary>mui/mui-x (@&#8203;mui/x-date-pickers)</summary>

### [`v7.9.0`](https://github.com/mui/mui-x/blob/HEAD/CHANGELOG.md#790)

[Compare Source](https://github.com/mui/mui-x/compare/v7.8.0...v7.9.0)

*Jul 5, 2024*

We'd like to offer a big thanks to the 7 contributors who made this release possible. Here are some highlights ✨:

-   🔄 Add loading overlay variants, including a skeleton loader option to the Data Grid component. See [Loading overlay docs](https://mui.com/x/react-data-grid/overlays/#loading-overlay) for more details.
-   🌳 Add `selectItem` and `getItemDOMElement` methods to the TreeView component public API
-   ⛏️ Make the `usePickersTranslations` hook public in the pickers component
-   🐞 Bugfixes



##### Data Grid

##### `@mui/x-data-grid@7.9.0`

-   \[DataGrid] Add skeleton loading overlay support ([#&#8203;13293](https://github.com/mui/mui-x/issues/13293)) [@&#8203;KenanYusuf](https://github.com/KenanYusuf)
-   \[DataGrid] Fix pagination when `pagination={undefined}` ([#&#8203;13349](https://github.com/mui/mui-x/issues/13349)) [@&#8203;sai6855](https://github.com/sai6855)

##### `@mui/x-data-grid-pro@7.9.0` [![pro](https://mui.com/r/x-pro-svg)](https://mui.com/r/x-pro-svg-link "Pro plan")

Same changes as in `@mui/x-data-grid@7.9.0`.

##### `@mui/x-data-grid-premium@7.9.0` [![premium](https://mui.com/r/x-premium-svg)](https://mui.com/r/x-premium-svg-link "Premium plan")

Same changes as in `@mui/x-data-grid-pro@7.9.0`.

##### Date and Time Pickers

##### `@mui/x-date-pickers@7.9.0`

-   \[pickers] Make the `usePickersTranslations` hook public ([#&#8203;13657](https://github.com/mui/mui-x/issues/13657)) [@&#8203;flaviendelangle](https://github.com/flaviendelangle)

##### `@mui/x-date-pickers-pro@7.9.0` [![pro](https://mui.com/r/x-pro-svg)](https://mui.com/r/x-pro-svg-link "Pro plan")

Same changes as in `@mui/x-date-pickers@7.9.0`.

##### Charts

##### `@mui/x-charts@7.9.0`

-   \[charts] Add Heatmap (unreleased) ([#&#8203;13209](https://github.com/mui/mui-x/issues/13209)) [@&#8203;alexfauquette](https://github.com/alexfauquette)
-   \[charts] Add initial `Zoom&Pan` to the Pro charts (unreleased) ([#&#8203;13405](https://github.com/mui/mui-x/issues/13405)) [@&#8203;JCQuintas](https://github.com/JCQuintas)
-   \[charts] Fix Axis Highlight on horizontal bar charts regression ([#&#8203;13717](https://github.com/mui/mui-x/issues/13717)) [@&#8203;JCQuintas](https://github.com/JCQuintas)
-   \[charts] Improve charts interaction for mobile users ([#&#8203;13692](https://github.com/mui/mui-x/issues/13692)) [@&#8203;JCQuintas](https://github.com/JCQuintas)
-   \[charts] Add documentation on how to disable the tooltip on charts ([#&#8203;13724](https://github.com/mui/mui-x/issues/13724)) [@&#8203;JCQuintas](https://github.com/JCQuintas)

##### Tree View

##### `@mui/x-tree-view@7.9.0`

-   \[TreeView] Add `selectItem` and `getItemDOMElement` methods to the public API ([#&#8203;13485](https://github.com/mui/mui-x/issues/13485)) [@&#8203;flaviendelangle](https://github.com/flaviendelangle)

##### Docs

-   \[docs] Fix custom "no results overlay" demo in dark mode ([#&#8203;13715](https://github.com/mui/mui-x/issues/13715)) [@&#8203;KenanYusuf](https://github.com/KenanYusuf)

##### Core

-   \[core] Add `react_next` workflow in CircleCI ([#&#8203;13360](https://github.com/mui/mui-x/issues/13360)) [@&#8203;cherniavskii](https://github.com/cherniavskii)
-   \[core] Create a new package to share utils across X packages ([#&#8203;13528](https://github.com/mui/mui-x/issues/13528)) [@&#8203;flaviendelangle](https://github.com/flaviendelangle)
-   \[core] Fix dependency setup ([#&#8203;13684](https://github.com/mui/mui-x/issues/13684)) [@&#8203;LukasTy](https://github.com/LukasTy)
-   \[core] Remove `jscodeshift-add-imports` package ([#&#8203;13720](https://github.com/mui/mui-x/issues/13720)) [@&#8203;LukasTy](https://github.com/LukasTy)
-   \[code-infra] Cleanup monorepo and `@mui/docs` usage ([#&#8203;13713](https://github.com/mui/mui-x/issues/13713)) [@&#8203;LukasTy](https://github.com/LukasTy)

</details>

<details>
<summary>trautonen/cdk-dns-validated-certificate (@&#8203;trautonen/cdk-dns-validated-certificate)</summary>

### [`v0.1.4`](https://github.com/trautonen/cdk-dns-validated-certificate/releases/tag/v0.1.4)

[Compare Source](https://github.com/trautonen/cdk-dns-validated-certificate/compare/v0.1.3...v0.1.4)

##### [0.1.4](https://github.com/trautonen/cdk-dns-validated-certificate/compare/v0.1.3...v0.1.4) (2024-07-02)

</details>

<details>
<summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/eslint-plugin)</summary>

### [`v7.15.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#7150-2024-07-01)

[Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v7.14.1...v7.15.0)

##### 🚀 Features

-   **eslint-plugin:** \[array-type] detect `Readonly<string[]>` case

-   **eslint-plugin:** back-port new rules around empty object types from v8

##### 🩹 Fixes

-   disable `EXPERIMENTAL_useProjectService` in `disabled-type-checked` shared config

-   **eslint-plugin:** \[no-unsafe-return] differentiate a types-error any from a true any

-   **eslint-plugin:** \[no-unsafe-call] differentiate a types-error any from a true any

##### ❤️  Thank You

-   auvred
-   Kim Sang Du
-   rgehbt
-   Vinccool96

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

</details>

<details>
<summary>typescript-eslint/typescript-eslint (@&#8203;typescript-eslint/parser)</summary>

### [`v7.15.0`](https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#7150-2024-07-01)

[Compare Source](https://github.com/typescript-eslint/typescript-eslint/compare/v7.14.1...v7.15.0)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.

</details>

<details>
<summary>aws/aws-cdk (aws-cdk)</summary>

### [`v2.148.0`](https://github.com/aws/aws-cdk/releases/tag/v2.148.0)

[Compare Source](https://github.com/aws/aws-cdk/compare/v2.147.3...v2.148.0)

##### Features

-   **lambda:** add grantInvokeLatestVersion to grant invoke only to latest function version ([#&#8203;29856](https://github.com/aws/aws-cdk/issues/29856)) ([61c28dd](https://github.com/aws/aws-cdk/commit/61c28dd79603ae50865f8b7a7f535ba4f7f69500)), closes [#&#8203;20177](https://github.com/aws/aws-cdk/issues/20177)
-   update L1 CloudFormation resource definitions ([#&#8203;30722](https://github.com/aws/aws-cdk/issues/30722)) ([4ceeced](https://github.com/aws/aws-cdk/commit/4ceecedd3d91465b29db21b10239937b99b5f79c)), closes [/docs.aws.amazon.com/service-terms/#&#8203;87](https://github.com/aws//docs.aws.amazon.com/service-terms//issues/87)
-   **codebuild:** adding `project.visibility` ([#&#8203;30103](https://github.com/aws/aws-cdk/issues/30103)) ([1bacb69](https://github.com/aws/aws-cdk/commit/1bacb69b6976dd75da78b45b07d6fec9306a6d72))
-   **codedeploy:** termination hook ([#&#8203;30644](https://github.com/aws/aws-cdk/issues/30644)) ([8f652a7](https://github.com/aws/aws-cdk/commit/8f652a7f9090502f70d2c733dd8a87619663ceb8))
-   **cognito:** add defaultRedirectUri to UserPoolClient ([#&#8203;30481](https://github.com/aws/aws-cdk/issues/30481)) ([f2c5f68](https://github.com/aws/aws-cdk/commit/f2c5f68b04e0cf89a7dcd453448988ba727c3363))
-   **eks:** eks pod identities ([#&#8203;30576](https://github.com/aws/aws-cdk/issues/30576)) ([9437b4d](https://github.com/aws/aws-cdk/commit/9437b4dbbea15db18ff2991d410e033cc3437001)), closes [/github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-eks/lib/oidc-provider.ts#L36](https://github.com/aws//github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-eks/lib/oidc-provider.ts/issues/L36) [/github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-eks/lib/oidc-provider.ts#L36](https://github.com/aws//github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-eks/lib/oidc-provider.ts/issues/L36) [/github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-iam/lib/role.ts#L373](https://github.com/aws//github.com/aws/aws-cdk/blob/b196b13b0b8a54dcacadf87fdbe744772a6e6c4d/packages/aws-cdk-lib/aws-iam/lib/role.ts/issues/L373) [#&#8203;30519](https://github.com/aws/aws-cdk/issues/30519)
-   **stepfunctions-tasks:** step functions task for cross-region AWS API call ([#&#8203;30061](https://github.com/aws/aws-cdk/issues/30061)) ([1397737](https://github.com/aws/aws-cdk/commit/1397737e16066d9101fd1c2fc85cd8396d738869)), closes [#&#8203;29918](https://github.com/aws/aws-cdk/issues/29918)
-   update L1 CloudFormation resource definitions ([#&#8203;30642](https://github.com/aws/aws-cdk/issues/30642)) ([2a659f0](https://github.com/aws/aws-cdk/commit/2a659f0ebbc039a03402b7f99a36dbf461e026aa))
-   **fsx:** add properties to enable automatic backups  for Lustre file system ([#&#8203;30343](https://github.com/aws/aws-cdk/issues/30343)) ([3b95777](https://github.com/aws/aws-cdk/commit/3b95777ee5dae32fd41481d81922d07c804a2c6b)), closes [#&#8203;30340](https://github.com/aws/aws-cdk/issues/30340)

##### Bug Fixes

-   **ecs:** let AsgCapacityProvider use IAutoScalingGroup only when Managed Termination Protection is disable ([#&#8203;30335](https://github.com/aws/aws-cdk/issues/30335)) ([efee07d](https://github.com/aws/aws-cdk/commit/efee07d6f17356b52b2a2e120ebe0404f554188b)), closes [#&#8203;29174](https://github.com/aws/aws-cdk/issues/29174)
-   **lambda-nodejs:** breaking change in esbuild causes import module error ([#&#8203;30726](https://github.com/aws/aws-cdk/issues/30726)) ([7f5ce4b](https://github.com/aws/aws-cdk/commit/7f5ce4bfe94b19efe6c0c8aa0ec850cdfc4b8ebb)), closes [#&#8203;30717](https://github.com/aws/aws-cdk/issues/30717)
-   **s3:** allow import S3 bucket with a legacy name ([#&#8203;30679](https://github.com/aws/aws-cdk/issues/30679)) ([e09126f](https://github.com/aws/aws-cdk/commit/e09126f6d97a52ee39811f8cbf874b722928debc)), closes [#&#8203;22640](https://github.com/aws/aws-cdk/issues/22640)
-   **s3-notifications:** unable to delete the existing S3 event notifications ([#&#8203;30610](https://github.com/aws/aws-cdk/issues/30610)) ([b880067](https://github.com/aws/aws-cdk/commit/b8800675d638bd866dc2444af895a650aea12ca7)), closes [#&#8203;28915](https://github.com/aws/aws-cdk/issues/28915)s too broad (under feature flag) ([#&#8203;30389](https://github.com/aws/aws-cdk/issues/30389)) ([8ebfade](https://github.com/aws/aws-cdk/commit/8ebfadeb8d7a8c15176ed9e5f106a49fc84040a6)), closes [#&#8203;30368](https://github.com/aws/aws-cdk/issues/30368)

##### Reverts

-   fix(core): overrideLogicalId validation ([#&#8203;30695](https://github.com/aws/aws-cdk/issues/30695)) ([0aa2be7](https://github.com/aws/aws-cdk/commit/0aa2be754ad667d40791557f0a8707b4ab6e6d4c)), closes [aws/aws-cdk#29708](https://github.com/aws/aws-cdk/issues/29708)
-   route53 CrossAccountZoneDelegationRecord fails at deployment time with imported `delegatedZone` ([#&#8203;30440](https://github.com/aws/aws-cdk/issues/30440))" ([#&#8203;30606](https://github.com/aws/aws-cdk/issues/30606)) ([95280a0](https://github.com/aws/aws-cdk/commit/95280a080a6e5a6f02932c80c092c8b7dac8ded8)), closes [#&#8203;30600](https://github.com/aws/aws-cdk/issues/30600)

***

##### Alpha modules (2.148.0-alpha.0)

##### Features

-   **apprunner:** add AutoScalingConfiguration for AppRunner Service ([#&#8203;30358](https://github.com/aws/aws-cdk/issues/30358)) ([a598508](https://github.com/aws/aws-cdk/commit/a598508e2a86c5932cbbbc4249cdc228bf2cbf39)), closes [#&#8203;30353](https://github.com/aws/aws-cdk/issues/30353)
-   **apprunner:** add ObservabilityConfiguration for AppRunner Service ([#&#8203;30359](https://github.com/aws/aws-cdk/issues/30359)) ([9e9cc27](https://github.com/aws/aws-cdk/commit/9e9cc277d55774b0b2e8887676ddb328eb662d74)), closes [#&#8203;22985](https://github.com/aws/aws-cdk/issues/22985)
-   **pipes-enrichments:** add Step Functions enrichment eventbridge pipes ([#&#8203;30495](https://github.com/aws/aws-cdk/issues/30495)) ([8b495f9](https://github.com/aws/aws-cdk/commit/8b495f9ec157c0b00674715f62b1bbcabf2096ac)), closes [#&#8203;29385](https://github.com/aws/aws-cdk/issues/29385)
-   **pipes-targets:** add lambda function ([#&#8203;30271](https://github.com/aws/aws-cdk/issues/30271)) ([f594fae](https://github.com/aws/aws-cdk/commit/f594fae922ea19c087c56405046098e5683d2c70)), closes [#&#8203;30270](https://github.com/aws/aws-cdk/issues/30270)

##### Bug Fixes

-   **apprunner:** auto deployment fails after new container image  pushed due to lack of a permission ([#&#8203;30630](https://github.com/aws/aws-cdk/issues/30630)) ([cce10b1](https://github.com/aws/aws-cdk/commit/cce10b1c1f0f764e39e734ad7d6c288b7ffb9da3)), closes [#&#8203;26640](https://github.com/aws/aws-cdk/issues/26640) [/github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-ecr/lib/repository.ts#L385](https://github.com/aws//github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-ecr/lib/repository.ts/issues/L385) [40aws-cdk/aws-apprunner-alpha/lib/service.ts#L1303](https://github.com/40aws-cdk/aws-apprunner-alpha/lib/service.ts/issues/L1303) [40aws-cdk/aws-apprunner-alpha/lib/service.ts#L1368](https://github.com/40aws-cdk/aws-apprunner-alpha/lib/service.ts/issues/L1368)

### [`v2.147.3`](https://github.com/aws/aws-cdk/releases/tag/v2.147.3)

[Compare Source](https://github.com/aws/aws-cdk/compare/v2.147.2...v2.147.3)

##### Bug Fixes

-   **lambda-nodejs:** breaking change in esbuild causes import module error ([#&#8203;30726](https://github.com/aws/aws-cdk/issues/30726)) ([06c14b1](https://github.com/aws/aws-cdk/commit/06c14b16d04353e9e108b58edc1450d018c24b12)), closes [#&#8203;30717](https://github.com/aws/aws-cdk/issues/30717)

***

#### Alpha modules (2.147.3-alpha.0)

</details>

<details>
<summary>aws/aws-sdk-js (aws-sdk)</summary>

### [`v2.1655.0`](https://github.com/aws/aws-sdk-js/blob/HEAD/CHANGELOG.md#216550)

[Compare Source](https://github.com/aws/aws-sdk-js/compare/v2.1654.0...v2.1655.0)

-   feature: ECR: This release for Amazon ECR makes change to bring the SDK into sync with the API.
-   feature: PaymentCryptographyData: Added further restrictions on logging of potentially sensitive inputs and outputs.
-   feature: QBusiness: Updates API to latest version.

### [`v2.1654.0`](https://github.com/aws/aws-sdk-js/blob/HEAD/CHANGELOG.md#216540)

[Compare Source](https://github.com/aws/aws-sdk-js/compare/v2.1653.0...v2.1654.0)

-   feature: Organizations: Added a new reason under ConstraintViolationException in RegisterDelegatedAdministrator API to prevent registering suspended accounts as delegated administrator of a service.
-   feature: Rekognition: This release adds support for tagging projects and datasets with the CreateProject and CreateDataset APIs.
-   feature: WorkSpaces: Fix create workspace bundle RootStorage/UserStorage to accept non null values

### [`v2.1653.0`](https://github.com/aws/aws-sdk-js/blob/HEAD/CHANGELOG.md#216530)

[Compare Source](https://github.com/aws/aws-sdk-js/compare/v2.1652.0...v2.1653.0)

-   feature: EC2: Documentation updates for Elastic Compute Cloud (EC2).
-   feature: FMS: Increases Customer API's ManagedServiceData length
-   feature: S3: Added response overrides to Head Object requests.

### [`v2.1652.0`](https://github.com/aws/aws-sdk-js/blob/HEAD/CHANGELOG.md#216520)

[Compare Source](https://github.com/aws/aws-sdk-js/compare/v2.1651.0...v2.1652.0)

-   feature: APIGateway: Add v2 smoke tests and smithy smokeTests trait for SDK testing.
-   feature: CognitoIdentity: Add v2 smoke tests and smithy smokeTests trait for SDK testing.
-   feature: Connect: Authentication profiles are Amazon Connect resources (in gated preview) that allow you to configure authentication settings for users in your contact center. This release adds support for new ListAuthenticationProfiles, DescribeAuthenticationProfile and UpdateAuthenticationProfile APIs.
-   feature: DocDB: Add v2 smoke tests and smithy smokeTests trait for SDK testing.
-   feature: EKS: Updates EKS managed node groups to support EC2 Capacity Blocks for ML
-   feature: PaymentCryptography: Added further restrictions on logging of potentially sensitive inputs and outputs.
-   feature: PaymentCryptographyData: Adding support for dynamic keys for encrypt, decrypt, re-encrypt and translate pin functions.  With this change, customers can use one-time TR-31 keys directly in dataplane operations without the need to first import them into the service.
-   feature: SWF: Add v2 smoke tests and smithy smokeTests trait for SDK testing.
-   feature: StepFunctions: Add v2 smoke tests and smithy smokeTests trait for SDK testing.

</details>

<details>
<summary>evanw/esbuild (esbuild)</summary>

### [`v0.23.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230)

[Compare Source](https://github.com/evanw/esbuild/compare/v0.22.0...v0.23.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.22.0` or `~0.22.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information.

-   Revert the recent change to avoid bundling dependencies for node ([#&#8203;3819](https://github.com/evanw/esbuild/issues/3819))

    This release reverts the recent change in version 0.22.0 that made `--packages=external` the default behavior with `--platform=node`.  The default is now back to `--packages=bundle`.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

-   Fix preserving collapsed JSX whitespace ([#&#8203;3818](https://github.com/evanw/esbuild/issues/3818))

    When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is an example:

    ```jsx
    // Original code
    <Foo>
      <Bar />
    </Foo>

    // Old output (with --jsx=preserve)
    <Foo><Bar /></Foo>;

    // New output (with --jsx=preserve)
    <Foo>
      <Bar />
    </Foo>;
    ```

### [`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information.

-   Omit packages from bundles by default when targeting node ([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874), [#&#8203;2830](https://github.com/evanw/esbuild/issues/2830), [#&#8203;2846](https://github.com/evanw/esbuild/issues/2846), [#&#8203;2915](https://github.com/evanw/esbuild/issues/2915), [#&#8203;3145](https://github.com/evanw/esbuild/issues/3145), [#&#8203;3294](https://github.com/evanw/esbuild/issues/3294), [#&#8203;3323](https://github.com/evanw/esbuild/issues/3323), [#&#8203;3582](https://github.com/evanw/esbuild/issues/3582), [#&#8203;3809](https://github.com/evanw/esbuild/issues/3809), [#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

    This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for `--platform=node`) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use `--packages=external` to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

    With this release, esbuild will now omit packages from the bundle by default when the platform is `node` (i.e. the previous behavior of `--packages=external` is now the default in this case). *Note that your dependencies must now be present on the file system when your bundle is run.* If you don't want this behavior, you can do `--packages=bundle` to allow packages to be included in the bundle (i.e. the previous default behavior). Note that `--packages=bundle` doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using `--external:` even when `--packages=bundle` is present.

    The `--packages=` setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of `/` or `.` or `..` are considered to be package imports. The only two exceptions to this rule are [subpath imports](https://nodejs.org/api/packages.html#subpath-imports) (which start with a `#` character) and TypeScript path remappings via `paths` and/or `baseUrl` in `tsconfig.json` (which are applied first).

-   Drop support for older platforms ([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

    This is because the Go programming language dropped support for these operating system versions in [Go 1.21](https://go.dev/doc/go1.21#windows), and this release updates esbuild from Go 1.20 to Go 1.22.

    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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

    In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's [release schedule](https://nodejs.org/en/about/previous-releases) for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the `esbuild-wasm` package and versions of node before node 17.4 (specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

    TypeScript 5.5 subtly changes the way `await using` behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in [microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

    The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: <https://2ality.com/2024/06/ecmascript-2024.html>. The only addition that's relevant for esbuild is the regular expression `/v` flag. With `--target=es2024`, regular expressions that use the `/v` flag will now be passed through untransformed instead of being transformed into a call to `new RegExp`.

-   Publish binaries for OpenBSD on 64-bit ARM ([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665), [#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

    With this release, you should now be able to install the `esbuild` npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

    This was contributed by [@&#8203;ikmckenz](https://github.com/ikmckenz).



</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 6am on saturday" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired.

---

 - [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/SvenKirschbaum/share.kirschbaum.cloud).
renovate bot added a commit to runtime-env/import-meta-env that referenced this pull request Jul 6, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [esbuild](https://github.com/evanw/esbuild) | [`0.19.5` ->
`0.23.0`](https://renovatebot.com/diffs/npm/esbuild/0.19.5/0.23.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.19.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.19.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.23.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.22.0...v0.23.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.22.0` or `~0.22.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Revert the recent change to avoid bundling dependencies for node
([#&#8203;3819](https://github.com/evanw/esbuild/issues/3819))

This release reverts the recent change in version 0.22.0 that made
`--packages=external` the default behavior with `--platform=node`. The
default is now back to `--packages=bundle`.

I've just been made aware that Amazon doesn't pin their dependencies in
their "AWS CDK" product, which means that whenever esbuild publishes a
new release, many people (potentially everyone?) using their SDK around
the world instantly starts using it without Amazon checking that it
works first. This change in version 0.22.0 happened to break their SDK.
I'm amazed that things haven't broken before this point. This revert
attempts to avoid these problems for Amazon's customers. Hopefully
Amazon will pin their dependencies in the future.

In addition, this is probably a sign that esbuild is used widely enough
that it now needs to switch to a more complicated release model. I may
have esbuild use a beta channel model for further development.

- Fix preserving collapsed JSX whitespace
([#&#8203;3818](https://github.com/evanw/esbuild/issues/3818))

When transformed, certain whitespace inside JSX elements is ignored
completely if it collapses to an empty string. However, the whitespace
should only be ignored if the JSX is being transformed, not if it's
being preserved. This release fixes a bug where esbuild was previously
incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is
an example:

    ```jsx
    // Original code
    <Foo>
      <Bar />
    </Foo>

    // Old output (with --jsx=preserve)
    <Foo><Bar /></Foo>;

    // New output (with --jsx=preserve)
    <Foo>
      <Bar />
    </Foo>;
    ```

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

###
[`v0.21.5`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0215)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.4...v0.21.5)

- Fix `Symbol.metadata` on classes without a class decorator
([#&#8203;3781](https://github.com/evanw/esbuild/issues/3781))

This release fixes a bug with esbuild's support for the [decorator
metadata
proposal](https://github.com/tc39/proposal-decorator-metadata).
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
([#&#8203;3792](https://github.com/evanw/esbuild/issues/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`:

    ```js
// 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`):

    ```js
// 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
([#&#8203;3797](https://github.com/evanw/esbuild/issues/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:

    ```ts
    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
([#&#8203;3782](https://github.com/evanw/esbuild/issues/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:

    ```json
    {
      "compilerOptions": {
        "paths": {
          "js/*": ["${configDir}/dist/js/*"]
        }
      }
    }
    ```

You can read more in [TypeScript's blog post about their upcoming 5.5
release](https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-rc/#the-configdir-template-variable-for-configuration-files).
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`
([#&#8203;3794](https://github.com/evanw/esbuild/issues/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`.

###
[`v0.21.4`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0214)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.3...v0.21.4)

- Update support for import assertions and import attributes in node
([#&#8203;3778](https://github.com/evanw/esbuild/issues/3778))

Import assertions (the `assert` keyword) have been removed from node
starting in v22.0.0. So esbuild will now strip them and generate a
warning with `--target=node22` or above:

▲ [WARNING] The "assert" keyword is not supported in the configured
target environment ("node22") [assert-to-with]

            example.mjs:1:40:
1 │ import json from "esbuild/package.json" assert { type: "json" }
                │                                         ~~~~~~
                ╵                                         with

          Did you mean to use "with" instead of "assert"?

Import attributes (the `with` keyword) have been backported to node 18
starting in v18.20.0. So esbuild will no longer strip them with
`--target=node18.N` if `N` is 20 or greater.

-   Fix `for await` transform when a label is present

This release fixes a bug where the `for await` transform, which wraps
the loop in a `try` statement, previously failed to also move the loop's
label into the `try` statement. This bug only affects code that uses
both of these features in combination. Here's an example of some
affected code:

    ```js
    // Original code
    async function test() {
      outer: for await (const x of [Promise.resolve([0, 1])]) {
        for (const y of x) if (y) break outer
        throw 'fail'
      }
    }

    // Old output (with --target=es6)
    function test() {
      return __async(this, null, function* () {
        outer: try {
for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp,
error; more = !(temp = yield iter.next()).done; more = false) {
            const x = temp.value;
            for (const y of x) if (y) break outer;
            throw "fail";
          }
        } catch (temp) {
          error = [temp];
        } finally {
          try {
            more && (temp = iter.return) && (yield temp.call(iter));
          } finally {
            if (error)
              throw error[0];
          }
        }
      });
    }

    // New output (with --target=es6)
    function test() {
      return __async(this, null, function* () {
        try {
outer: for (var iter = __forAwait([Promise.resolve([0, 1])]), more,
temp, error; more = !(temp = yield iter.next()).done; more = false) {
            const x = temp.value;
            for (const y of x) if (y) break outer;
            throw "fail";
          }
        } catch (temp) {
          error = [temp];
        } finally {
          try {
            more && (temp = iter.return) && (yield temp.call(iter));
          } finally {
            if (error)
              throw error[0];
          }
        }
      });
    }
    ```

- Do additional constant folding after cross-module enum inlining
([#&#8203;3416](https://github.com/evanw/esbuild/issues/3416),
[#&#8203;3425](https://github.com/evanw/esbuild/issues/3425))

This release adds a few more cases where esbuild does constant folding
after cross-module enum inlining.

    ```ts
    // Original code: enum.ts
    export enum Platform {
      WINDOWS = 'windows',
      MACOS = 'macos',
      LINUX = 'linux',
    }

    // Original code: main.ts
    import { Platform } from './enum';
    declare const PLATFORM: string;
    export function logPlatform() {
      if (PLATFORM == Platform.WINDOWS) console.log('Windows');
      else if (PLATFORM == Platform.MACOS) console.log('macOS');
      else if (PLATFORM == Platform.LINUX) console.log('Linux');
      else console.log('Other');
    }

// Old output (with --bundle '--define:PLATFORM="macos"' --minify
--format=esm)
function
n(){"windows"=="macos"?console.log("Windows"):"macos"=="macos"?console.log("macOS"):"linux"=="macos"?console.log("Linux"):console.log("Other")}export{n
as logPlatform};

// New output (with --bundle '--define:PLATFORM="macos"' --minify
--format=esm)
    function n(){console.log("macOS")}export{n as logPlatform};
    ```

- Pass import attributes to on-resolve plugins
([#&#8203;3384](https://github.com/evanw/esbuild/issues/3384),
[#&#8203;3639](https://github.com/evanw/esbuild/issues/3639),
[#&#8203;3646](https://github.com/evanw/esbuild/issues/3646))

With this release, on-resolve plugins will now have access to the import
attributes on the import via the `with` property of the arguments
object. This mirrors the `with` property of the arguments object that's
already passed to on-load plugins. In addition, you can now pass `with`
to the `resolve()` API call which will then forward that value on to all
relevant plugins. Here's an example of a plugin that can now be written:

    ```js
    const examplePlugin = {
      name: 'Example plugin',
      setup(build) {
        build.onResolve({ filter: /.*/ }, args => {
          if (args.with.type === 'external')
            return { external: true }
        })
      }
    }

    require('esbuild').build({
      stdin: {
        contents: `
          import foo from "./foo" with { type: "external" }
          foo()
        `,
      },
      bundle: true,
      format: 'esm',
      write: false,
      plugins: [examplePlugin],
    }).then(result => {
      console.log(result.outputFiles[0].text)
    })
    ```

- Formatting support for the `@position-try` rule
([#&#8203;3773](https://github.com/evanw/esbuild/issues/3773))

Chrome shipped this new CSS at-rule in version 125 as part of the [CSS
anchor positioning
API](https://developer.chrome.com/blog/anchor-positioning-api). With
this release, esbuild now knows to expect a declaration list inside of
the `@position-try` body block and will format it appropriately.

- Always allow internal string import and export aliases
([#&#8203;3343](https://github.com/evanw/esbuild/issues/3343))

Import and export names can be string literals in ES2022+. Previously
esbuild forbid any usage of these aliases when the target was below
ES2022. Starting with this release, esbuild will only forbid such usage
when the alias would otherwise end up in output as a string literal.
String literal aliases that are only used internally in the bundle and
are "compiled away" are no longer errors. This makes it possible to use
string literal aliases with esbuild's `inject` feature even when the
target is earlier than ES2022.

###
[`v0.21.3`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0213)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.2...v0.21.3)

- Implement the decorator metadata proposal
([#&#8203;3760](https://github.com/evanw/esbuild/issues/3760))

This release implements the [decorator metadata
proposal](https://github.com/tc39/proposal-decorator-metadata), which
is a sub-proposal of the [decorators
proposal](https://github.com/tc39/proposal-decorators). Microsoft
shipped the decorators proposal in [TypeScript
5.0](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators)
and the decorator metadata proposal in [TypeScript
5.2](https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/#decorator-metadata),
so it's important that esbuild also supports both of these features.
Here's a quick example:

    ```js
    // Shim the "Symbol.metadata" symbol
    Symbol.metadata ??= Symbol('Symbol.metadata')

    const track = (_, context) => {
      (context.metadata.names ||= []).push(context.name)
    }

    class Foo {
      @&#8203;track foo = 1
      @&#8203;track bar = 2
    }

    // Prints ["foo", "bar"]
    console.log(Foo[Symbol.metadata].names)
    ```

    **⚠️ WARNING ⚠️**

This proposal has been marked as "stage 3" which means "recommended for
implementation". However, it's still a work in progress and isn't a part
of JavaScript yet, so keep in mind that any code that uses JavaScript
decorator metadata may need to be updated as the feature continues to
evolve. If/when that happens, I will update esbuild's implementation to
match the specification. I will not be supporting old versions of the
specification.

- Fix bundled decorators in derived classes
([#&#8203;3768](https://github.com/evanw/esbuild/issues/3768))

In certain cases, bundling code that uses decorators in a derived class
with a class body that references its own class name could previously
generate code that crashes at run-time due to an incorrect variable
name. This problem has been fixed. Here is an example of code that was
compiled incorrectly before this fix:

    ```js
    class Foo extends Object {
      @&#8203;(x => x) foo() {
        return Foo
      }
    }
    console.log(new Foo().foo())
    ```

- Fix `tsconfig.json` files inside symlinked directories
([#&#8203;3767](https://github.com/evanw/esbuild/issues/3767))

This release fixes an issue with a scenario involving a `tsconfig.json`
file that `extends` another file from within a symlinked directory that
uses the `paths` feature. In that case, the implicit `baseURL` value
should be based on the real path (i.e. after expanding all symbolic
links) instead of the original path. This was already done for other
files that esbuild resolves but was not yet done for `tsconfig.json`
because it's special-cased (the regular path resolver can't be used
because the information inside `tsconfig.json` is involved in path
resolution). Note that this fix no longer applies if the
`--preserve-symlinks` setting is enabled.

###
[`v0.21.2`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0212)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.1...v0.21.2)

- Correct `this` in field and accessor decorators
([#&#8203;3761](https://github.com/evanw/esbuild/issues/3761))

This release changes the value of `this` in initializers for class field
and accessor decorators from the module-level `this` value to the
appropriate `this` value for the decorated element (either the class or
the instance). It was previously incorrect due to lack of test coverage.
Here's an example of a decorator that doesn't work without this change:

    ```js
    const dec = () => function() { this.bar = true }
    class Foo { @&#8203;dec static foo }
    console.log(Foo.bar) // Should be "true"
    ```

- Allow `es2023` as a target environment
([#&#8203;3762](https://github.com/evanw/esbuild/issues/3762))

TypeScript recently [added
`es2023`](https://github.com/microsoft/TypeScript/pull/58140) as a
compilation target, so esbuild now supports this too. There is no
difference between a target of `es2022` and `es2023` as far as esbuild
is concerned since the 2023 edition of JavaScript doesn't introduce any
new syntax features.

###
[`v0.21.1`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0211)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.0...v0.21.1)

- Fix a regression with `--keep-names`
([#&#8203;3756](https://github.com/evanw/esbuild/issues/3756))

The previous release introduced a regression with the `--keep-names`
setting and object literals with `get`/`set` accessor methods, in which
case the generated code contained syntax errors. This release fixes the
regression:

    ```js
    // Original code
    x = { get y() {} }

    // Output from version 0.21.0 (with --keep-names)
    x = { get y: /* @&#8203;__PURE__ */ __name(function() {
    }, "y") };

    // Output from this version (with --keep-names)
    x = { get y() {
    } };
    ```

###
[`v0.21.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0210)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.20.2...v0.21.0)

This release doesn't contain any deliberately-breaking changes. However,
it contains a very complex new feature and while all of esbuild's tests
pass, I would not be surprised if an important edge case turns out to be
broken. So I'm releasing this as a breaking change release to avoid
causing any trouble. As usual, make sure to test your code when you
upgrade.

- Implement the JavaScript decorators proposal
([#&#8203;104](https://github.com/evanw/esbuild/issues/104))

With this release, esbuild now contains an implementation of the
upcoming [JavaScript decorators
proposal](https://github.com/tc39/proposal-decorators). This is the
same feature that shipped in [TypeScript
5.0](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators)
and has been highly-requested on esbuild's issue tracker. You can read
more about them in that blog post and in this other (now slightly
outdated) extensive blog post here:
https://2ality.com/2022/10/javascript-decorators.html. Here's a quick
example:

    ```js
    const log = (fn, context) => function() {
      console.log(`before ${context.name}`)
      const it = fn.apply(this, arguments)
      console.log(`after ${context.name}`)
      return it
    }

    class Foo {
      @&#8203;log static foo() {
        console.log('in foo')
      }
    }

    // Logs "before foo", "in foo", "after foo"
    Foo.foo()
    ```

Note that this feature is different than the existing "TypeScript
experimental decorators" feature that esbuild already implements. It
uses similar syntax but behaves very differently, and the two are not
compatible (although it's sometimes possible to write decorators that
work with both). TypeScript experimental decorators will still be
supported by esbuild going forward as they have been around for a long
time, are very widely used, and let you do certain things that are not
possible with JavaScript decorators (such as decorating function
parameters). By default esbuild will parse and transform JavaScript
decorators, but you can tell esbuild to parse and transform TypeScript
experimental decorators instead by setting `"experimentalDecorators":
true` in your `tsconfig.json` file.

Probably at least half of the work for this feature went into creating a
test suite that exercises many of the proposal's edge cases:
https://github.com/evanw/decorator-tests. It has given me a reasonable
level of confidence that esbuild's initial implementation is acceptable.
However, I don't have access to a significant sample of real code that
uses JavaScript decorators. If you're currently using JavaScript
decorators in a real code base, please try out esbuild's implementation
and let me know if anything seems off.

    **⚠️ WARNING ⚠️**

This proposal has been in the works for a very long time (work began
around 10 years ago in 2014) and it is finally getting close to becoming
part of the JavaScript language. However, it's still a work in progress
and isn't a part of JavaScript yet, so keep in mind that any code that
uses JavaScript decorators may need to be updated as the feature
continues to evolve. The decorators proposal is pretty close to its
final form but it can and likely will undergo some small behavioral
adjustments before it ends up becoming a part of the standard. If/when
that happens, I will update esbuild's implementation to match the
specification. I will not be supporting old versions of the
specification.

-   Optimize the generated code for private methods

Previously when lowering private methods for old browsers, esbuild would
generate one `WeakSet` for each private method. This mirrors similar
logic for generating one `WeakSet` for each private field. Using a
separate `WeakMap` for private fields is necessary as their assignment
can be observable:

    ```js
    let it
    class Bar {
      constructor() {
        it = this
      }
    }
    class Foo extends Bar {
      #x = 1
      #y = null.foo
      static check() {
        console.log(#x in it, #y in it)
      }
    }
    try { new Foo } catch {}
    Foo.check()
    ```

This prints `true false` because this partially-initialized instance has
`#x` but not `#y`. In other words, it's not true that all class
instances will always have all of their private fields. However, the
assignment of private methods to a class instance is not observable. In
other words, it's true that all class instances will always have all of
their private methods. This means esbuild can lower private methods into
code where all methods share a single `WeakSet`, which is smaller,
faster, and uses less memory. Other JavaScript processing tools such as
the TypeScript compiler already make this optimization. Here's what this
change looks like:

    ```js
    // Original code
    class Foo {
      #x() { return this.#x() }
      #y() { return this.#y() }
      #z() { return this.#z() }
    }

    // Old output (--supported:class-private-method=false)
    var _x, x_fn, _y, y_fn, _z, z_fn;
    class Foo {
      constructor() {
        __privateAdd(this, _x);
        __privateAdd(this, _y);
        __privateAdd(this, _z);
      }
    }
    _x = new WeakSet();
    x_fn = function() {
      return __privateMethod(this, _x, x_fn).call(this);
    };
    _y = new WeakSet();
    y_fn = function() {
      return __privateMethod(this, _y, y_fn).call(this);
    };
    _z = new WeakSet();
    z_fn = function() {
      return __privateMethod(this, _z, z_fn).call(this);
    };

    // New output (--supported:class-private-method=false)
    var _Foo_instances, x_fn, y_fn, z_fn;
    class Foo {
      constructor() {
        __privateAdd(this, _Foo_instances);
      }
    }
    _Foo_instances = new WeakSet();
    x_fn = function() {
      return __privateMethod(this, _Foo_instances, x_fn).call(this);
    };
    y_fn = function() {
      return __privateMethod(this, _Foo_instances, y_fn).call(this);
    };
    z_fn = function() {
      return __privateMethod(this, _Foo_instances, z_fn).call(this);
    };
    ```

- Fix an obscure bug with lowering class members with computed property
keys

When class members that use newer syntax features are transformed for
older target environments, they sometimes need to be relocated. However,
care must be taken to not reorder any side effects caused by computed
property keys. For example, the following code must evaluate `a()` then
`b()` then `c()`:

    ```js
    class Foo {
      [a()]() {}
      [b()];
      static { c() }
    }
    ```

Previously esbuild did this by shifting the computed property key
*forward* to the next spot in the evaluation order. Classes evaluate all
computed keys first and then all static class elements, so if the last
computed key needs to be shifted, esbuild previously inserted a static
block at start of the class body, ensuring it came before all other
static class elements:

    ```js
    var _a;
    class Foo {
      constructor() {
        __publicField(this, _a);
      }
      static {
        _a = b();
      }
      [a()]() {
      }
      static {
        c();
      }
    }
    ```

However, this could cause esbuild to accidentally generate a syntax
error if the computed property key contains code that isn't allowed in a
static block, such as an `await` expression. With this release, esbuild
fixes this problem by shifting the computed property key *backward* to
the previous spot in the evaluation order instead, which may push it
into the `extends` clause or even before the class itself:

    ```js
    // Original code
    class Foo {
      [a()]() {}
      [await b()];
      static { c() }
    }

    // Old output (with --supported:class-field=false)
    var _a;
    class Foo {
      constructor() {
        __publicField(this, _a);
      }
      static {
        _a = await b();
      }
      [a()]() {
      }
      static {
        c();
      }
    }

    // New output (with --supported:class-field=false)
    var _a, _b;
    class Foo {
      constructor() {
        __publicField(this, _a);
      }
      [(_b = a(), _a = await b(), _b)]() {
      }
      static {
        c();
      }
    }
    ```

-   Fix some `--keep-names` edge cases

The [`NamedEvaluation` syntax-directed
operation](https://tc39.es/ecma262/#sec-runtime-semantics-namedevaluation)
in the JavaScript specification gives certain anonymous expressions a
`name` property depending on where they are in the syntax tree. For
example, the following initializers convey a `name` value:

    ```js
    var foo = function() {}
    var bar = class {}
    console.log(foo.name, bar.name)
    ```

When you enable esbuild's `--keep-names` setting, esbuild generates
additional code to represent this `NamedEvaluation` operation so that
the value of the `name` property persists even when the identifiers are
renamed (e.g. due to minification).

However, I recently learned that esbuild's implementation of
`NamedEvaluation` is missing a few cases. Specifically esbuild was
missing property definitions, class initializers, logical-assignment
operators. These cases should now all be handled:

    ```js
    var obj = { foo: function() {} }
    class Foo0 { foo = function() {} }
    class Foo1 { static foo = function() {} }
    class Foo2 { accessor foo = function() {} }
    class Foo3 { static accessor foo = function() {} }
    foo ||= function() {}
    foo &&= function() {}
    foo ??= function() {}
    ```

###
[`v0.20.2`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0202)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.20.1...v0.20.2)

- Support TypeScript experimental decorators on `abstract` class fields
([#&#8203;3684](https://github.com/evanw/esbuild/issues/3684))

With this release, you can now use TypeScript experimental decorators on
`abstract` class fields. This was silently compiled incorrectly in
esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to
esbuild 0.20.1. Code such as the following should now work correctly:

    ```ts
    // Original code
    const log = (x: any, y: string) => console.log(y)
    abstract class Foo { @&#8203;log abstract foo: string }
    new class extends Foo { foo = '' }

// Old output (with --loader=ts
--tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
    const log = (x, y) => console.log(y);
    class Foo {
    }
    new class extends Foo {
      foo = "";
    }();

// New output (with --loader=ts
--tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
    const log = (x, y) => console.log(y);
    class Foo {
    }
    __decorateClass([
      log
    ], Foo.prototype, "foo", 2);
    new class extends Foo {
      foo = "";
    }();
    ```

- JSON loader now preserves `__proto__` properties
([#&#8203;3700](https://github.com/evanw/esbuild/issues/3700))

Copying JSON source code into a JavaScript file will change its meaning
if a JSON object contains the `__proto__` key. A literal `__proto__`
property in a JavaScript object literal sets the prototype of the object
instead of adding a property named `__proto__`, while a literal
`__proto__` property in a JSON object literal just adds a property named
`__proto__`. With this release, esbuild will now work around this
problem by converting JSON to JavaScript with a computed property key in
this case:

    ```js
    // Original code
    import data from 'data:application/json,{"__proto__":{"fail":true}}'
    if (Object.getPrototypeOf(data)?.fail) throw 'fail'

    // Old output (with --bundle)
    (() => {
      // <data:application/json,{"__proto__":{"fail":true}}>
      var json_proto_fail_true_default = { __proto__: { fail: true } };

      // entry.js
      if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
        throw "fail";
    })();

    // New output (with --bundle)
    (() => {
      // <data:application/json,{"__proto__":{"fail":true}}>
var json_proto_fail_true_default = { ["__proto__"]: { fail: true } };

      // example.mjs
      if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
        throw "fail";
    })();
    ```

- Improve dead code removal of `switch` statements
([#&#8203;3659](https://github.com/evanw/esbuild/issues/3659))

With this release, esbuild will now remove `switch` statements in
branches when minifying if they are known to never be evaluated:

    ```js
    // Original code
    if (true) foo(); else switch (bar) { case 1: baz(); break }

    // Old output (with --minify)
    if(1)foo();else switch(bar){case 1:}

    // New output (with --minify)
    foo();
    ```

- Empty enums should behave like an object literal
([#&#8203;3657](https://github.com/evanw/esbuild/issues/3657))

TypeScript allows you to create an empty enum and add properties to it
at run time. While people usually use an empty object literal for this
instead of a TypeScript enum, esbuild's enum transform didn't anticipate
this use case and generated `undefined` instead of `{}` for an empty
enum. With this release, you can now use an empty enum to generate an
empty object literal.

    ```ts
    // Original code
    enum Foo {}

    // Old output (with --loader=ts)
    var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
    })(Foo || {});

    // New output (with --loader=ts)
    var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
      return Foo2;
    })(Foo || {});
    ```

- Handle Yarn Plug'n'Play edge case with `tsconfig.json`
([#&#8203;3698](https://github.com/evanw/esbuild/issues/3698))

Previously a `tsconfig.json` file that `extends` another file in a
package with an `exports` map failed to work when Yarn's Plug'n'Play
resolution was active. This edge case should work now starting with this
release.

- Work around issues with Deno 1.31+
([#&#8203;3682](https://github.com/evanw/esbuild/issues/3682))

Version 0.20.0 of esbuild changed how the esbuild child process is run
in esbuild's API for Deno. Previously it used `Deno.run` but that API is
being removed in favor of `Deno.Command`. As part of this change,
esbuild is now calling the new `unref` function on esbuild's long-lived
child process, which is supposed to allow Deno to exit when your code
has finished running even though the child process is still around
(previously you had to explicitly call esbuild's `stop()` function to
terminate the child process for Deno to be able to exit).

However, this introduced a problem for Deno's testing API which now
fails some tests that use esbuild with `error: Promise resolution is
still pending but the event loop has already resolved`. It's unclear to
me why this is happening. The call to `unref` was recommended by someone
on the Deno core team, and calling Node's equivalent `unref` API has
been working fine for esbuild in Node for a long time. It could be that
I'm using it incorrectly, or that there's some reference counting and/or
garbage collection bug in Deno's internals, or that Deno's `unref` just
works differently than Node's `unref`. In any case, it's not good for
Deno tests that use esbuild to be failing.

In this release, I am removing the call to `unref` to fix this issue.
This means that you will now have to call esbuild's `stop()` function to
allow Deno to exit, just like you did before esbuild version 0.20.0 when
this regression was introduced.

Note: This regression wasn't caught earlier because Deno doesn't seem to
fail tests that have outstanding `setTimeout` calls, which esbuild's
test harness was using to enforce a maximum test runtime. Adding a
`setTimeout` was allowing esbuild's Deno tests to succeed. So this
regression doesn't necessarily apply to all people using tests in Deno.

###
[`v0.20.1`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0201)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.20.0...v0.20.1)

- Fix a bug with the CSS nesting transform
([#&#8203;3648](https://github.com/evanw/esbuild/issues/3648))

This release fixes a bug with the CSS nesting transform for older
browsers where the generated CSS could be incorrect if a selector list
contained a pseudo element followed by another selector. The bug was
caused by incorrectly mutating the parent rule's selector list when
filtering out pseudo elements for the child rules:

    ```css
    /* Original code */
    .foo {
      &:after,
      & .bar {
        color: red;
      }
    }

    /* Old output (with --supported:nesting=false) */
    .foo .bar,
    .foo .bar {
      color: red;
    }

    /* New output (with --supported:nesting=false) */
    .foo:after,
    .foo .bar {
      color: red;
    }
    ```

- Constant folding for JavaScript inequality operators
([#&#8203;3645](https://github.com/evanw/esbuild/issues/3645))

This release introduces constant folding for the `< > <= >=` operators.
The minifier will now replace these operators with `true` or `false`
when both sides are compile-time numeric or string constants:

    ```js
    // Original code
    console.log(1 < 2, '🍕' > '🧀')

    // Old output (with --minify)
    console.log(1<2,"🍕">"🧀");

    // New output (with --minify)
    console.log(!0,!1);
    ```

- Better handling of `__proto__` edge cases
([#&#8203;3651](https://github.com/evanw/esbuild/pull/3651))

JavaScript object literal syntax contains a special case where a
non-computed property with a key of `__proto__` sets the prototype of
the object. This does not apply to computed properties or to properties
that use the shorthand property syntax introduced in ES6. Previously
esbuild didn't correctly preserve the "sets the prototype" status of
properties inside an object literal, meaning a property that sets the
prototype could accidentally be transformed into one that doesn't and
vice versa. This has now been fixed:

    ```js
    // Original code
    function foo(__proto__) {
      return { __proto__: __proto__ } // Note: sets the prototype
    }
    function bar(__proto__, proto) {
      {
        let __proto__ = proto
        return { __proto__ } // Note: doesn't set the prototype
      }
    }

    // Old output
    function foo(__proto__) {
return { __proto__ }; // Note: no longer sets the prototype (WRONG)
    }
    function bar(__proto__, proto) {
      {
        let __proto__2 = proto;
return { __proto__: __proto__2 }; // Note: now sets the prototype
(WRONG)
      }
    }

    // New output
    function foo(__proto__) {
return { __proto__: __proto__ }; // Note: sets the prototype (correct)
    }
    function bar(__proto__, proto) {
      {
        let __proto__2 = proto;
return { ["__proto__"]: __proto__2 }; // Note: doesn't set the prototype
(correct)
      }
    }
    ```

- Fix cross-platform non-determinism with CSS color space
transformations
([#&#8203;3650](https://github.com/evanw/esbuild/issues/3650))

The Go compiler takes advantage of "fused multiply and add" (FMA)
instructions on certain processors which do the operation `x*y + z`
without intermediate rounding. This causes esbuild's CSS color space
math to differ on different processors (currently `ppc64le` and
`s390x`), which breaks esbuild's guarantee of deterministic output. To
avoid this, esbuild's color space math now inserts a `float64()` cast
around every single math operation. This tells the Go compiler not to
use the FMA optimization.

- Fix a crash when resolving a path from a directory that doesn't exist
([#&#8203;3634](https://github.com/evanw/esbuild/issues/3634))

This release fixes a regression where esbuild could crash when resolving
an absolute path if the source directory for the path resolution
operation doesn't exist. While this situation doesn't normally come up,
it could come up when running esbuild concurrently with another
operation that mutates the file system as esbuild is doing a build (such
as using `git` to switch branches). The underlying problem was a
regression that was introduced in version 0.18.0.

###
[`v0.20.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0200)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.19.12...v0.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](https://docs.npmjs.com/cli/v6/using-npm/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
([#&#8203;3609](https://github.com/evanw/esbuild/issues/3609),
[#&#8203;3611](https://github.com/evanw/esbuild/pull/3611))

[Deno 1.40.0](https://deno.com/blog/v1.40) 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`
([#&#8203;3341](https://github.com/evanw/esbuild/issues/3341),
[#&#8203;3608](https://github.com/evanw/esbuild/issues/3608))

In [version
0.18.0](https://github.com/evanw/esbuild/releases/v0.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.

###
[`v0.19.12`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01912)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.19.11...v0.19.12)

- The "preserve" JSX mode now preserves JSX text verbatim
([#&#8203;3605](https://github.com/evanw/esbuild/issues/3605))

The [JSX specification](https://facebook.github.io/jsx/) deliberately
doesn't specify how JSX text is supposed to be interpreted and there is
no canonical way to interpret JSX text. Two most popular interpretations
are Babel and TypeScript. Yes [they are
different](https://twitter.com/jarredsumner/status/1456118847937781764)
(esbuild [deliberately follows
TypeScript](https://twitter.com/evanwallace/status/1456122279453208576)
by the way).

Previously esbuild normalized text to the TypeScript interpretation when
the "preserve" JSX mode is active. However, "preserve" should arguably
reproduce the original JSX text verbatim so that whatever JSX transform
runs after esbuild is free to interpret it however it wants. So with
this release, esbuild will now pass JSX text through unmodified:

    ```jsx
    // Original code
    let el =
      <a href={'/'} title='&apos;&quot;'> some text
        {foo}
          more text </a>

    // Old output (with --loader=jsx --jsx=preserve)
    let el = <a href="/" title={`'"`}>
      {" some text"}
      {foo}
      {"more text "}
    </a>;

    // New output (with --loader=jsx --jsx=preserve)
    let el = <a href={"/"} title='&apos;&quot;'> some text
        {foo}
          more text </a>;
    ```

-   Allow JSX elements as JSX attribute values

JSX has an obscure feature where you can use JSX elements in attribute
position without surrounding them with `{...}`. It looks like this:

    ```jsx
    let el = <div data-ab=<><a/><b/></>/>;
    ```

I think I originally didn't implement it even though it's part of the
[JSX specification](https://facebook.github.io/jsx/) because it
previously didn't work in TypeScript (and potentially also in Babel?).
However, support for it was [silently added in TypeScript
4.8](https://github.com/microsoft/TypeScript/pull/47994) without me
noticing and Babel has also since fixed their [bugs regarding this
feature](https://github.com/babel/babel/pull/6006). So I'm adding it
to esbuild too now that I know it's widely supported.

Keep in mind that there is some ongoing discussion about [removing this
feature from JSX](https://github.com/facebook/jsx/issues/53). I agree
that the syntax seems out of place (it does away with the elegance of
"JSX is basically just XML with `{...}` escapes" for something arguably
harder to read, which doesn't seem like a good trade-off), but it's in
the specification and TypeScript and Babel both implement it so I'm
going to have esbuild implement it too. However, I reserve the right to
remove it from esbuild if it's ever removed from the specification in
the future. So use it with caution.

- Fix a bug with TypeScript type parsing
([#&#8203;3574](https://github.com/evanw/esbuild/issues/3574))

This release fixes a bug with esbuild's TypeScript parser where a
conditional type containing a union type that ends with an infer type
that ends with a constraint could fail to parse. This was caused by the
"don't parse a conditional type" flag not getting passed through the
union type parser. Here's an example of valid TypeScript code that
previously failed to parse correctly:

    ```ts
type InferUnion<T> = T extends { a: infer U extends number } | infer U
extends number ? U : never
    ```

###
[`v0.19.11`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#01911)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.19.10...v0.19.11)

- Fix TypeScript-specific class transform edge case
([#&#8203;3559](https://github.com/evanw/esbuild/issues/3559))

The previous release introduced an optimization that avoided
transforming `super()` in the class constructor for TypeScript code
compiled with `useDefineForClassFields` set to `false` if all class
instance fields have no initializers. The rationale was that in this
case, all class instance fields are omitted in the output so no changes
to the constructor are needed. However, if all of this is the case *and*
there are `#private` instance fields with initializers, those private
instance field initializers were still being moved into the constructor.
This was problematic because they were being inserted before the call to
`super()` (since `super()` is now no longer transformed in that case).
This release introduces an additional optimization that avoids moving
the private instance field initializers into the constructor in this
edge case, which generates smaller code, matches the TypeScript
compiler's output more closely, and avoids this bug:

    ```ts
    // Original code
    class Foo extends Bar {
      #private = 1;
      public: any;
      constructor() {
        super();
      }
    }

    // Old output (with esbuild v0.19.9)
    class Foo extends Bar {
      constructor() {
        super();
        this.#private = 1;
      }
      #private;
    }

    // Old output (with esbuild v0.19.10)
    class Foo extends Bar {
      constructor() {
        this.#private = 1;
        super();
      }
      #private;
    }

    // New output
    class Foo extends Bar {
      #private = 1;
      constructor() {
        super();
      }
    }
    ```

- Minifier: allow reording a primitive past a side-effect
([#&#8203;3568](https://github.com/evanw/esbuild/issues/3568))

The minifier previously allowed reordering a side-effect past a
primitive, but didn't handle the case of reordering a primitive past a
side-effect. This additional case is now handled:

    ```js
    // Original code
    function f() {
      let x = false;
      let y = x;
      const boolean = y;
let frag = $.template(`<p contenteditable="${boolean}">hello
world</p>`);
      return frag;
    }

    // Old output (with --minify)
function f(){const e=!1;return $.template(`<p
contenteditable="${e}">hello world</p>`)}

    // New output (with --minify)
function f(){return $.template('<p contenteditable="false">hello
world</p>')}
    ```

- Minifier: consider properties named using known `Symbol` instances to
be side-effect free
([#&#8203;3561](https://github.com/evanw/esbuild/issues/3561))

Many things in JavaScript can have side effects including property
accesses and ToString operations, so using a symbol such as
`Symbol.iterator` as a computed prope

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/runtime-env/import-meta-env).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuOSIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS45IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
github-merge-queue bot pushed a commit to AmadeusITGroup/otter that referenced this pull request Jul 9, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [esbuild](https://github.com/evanw/esbuild) | [`~0.21.0` ->
`~0.23.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.5/0.23.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.23.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.22.0...v0.23.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.22.0` or `~0.22.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Revert the recent change to avoid bundling dependencies for node
([#&#8203;3819](https://github.com/evanw/esbuild/issues/3819))

This release reverts the recent change in version 0.22.0 that made
`--packages=external` the default behavior with `--platform=node`. The
default is now back to `--packages=bundle`.

I've just been made aware that Amazon doesn't pin their dependencies in
their "AWS CDK" product, which means that whenever esbuild publishes a
new release, many people (potentially everyone?) using their SDK around
the world instantly starts using it without Amazon checking that it
works first. This change in version 0.22.0 happened to break their SDK.
I'm amazed that things haven't broken before this point. This revert
attempts to avoid these problems for Amazon's customers. Hopefully
Amazon will pin their dependencies in the future.

In addition, this is probably a sign that esbuild is used widely enough
that it now needs to switch to a more complicated release model. I may
have esbuild use a beta channel model for further development.

- Fix preserving collapsed JSX whitespace
([#&#8203;3818](https://github.com/evanw/esbuild/issues/3818))

When transformed, certain whitespace inside JSX elements is ignored
completely if it collapses to an empty string. However, the whitespace
should only be ignored if the JSX is being transformed, not if it's
being preserved. This release fixes a bug where esbuild was previously
incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is
an example:

    ```jsx
    // Original code
    <Foo>
      <Bar />
    </Foo>

    // Old output (with --jsx=preserve)
    <Foo><Bar /></Foo>;

    // New output (with --jsx=preserve)
    <Foo>
      <Bar />
    </Foo>;
    ```

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about these
updates again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/AmadeusITGroup/otter).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuOSIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS45IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
alecthomas pushed a commit to alecthomas/chroma that referenced this pull request Jul 11, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Type | Update | Change | Age | Adoption | Passing |
Confidence |
|---|---|---|---|---|---|---|---|
| [esbuild](https://github.com/evanw/esbuild) | | minor | `0.21.5` ->
`0.23.0` |
[![age](https://developer.mend.io/api/mc/badges/age/hermit/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/hermit/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/hermit/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/hermit/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [github.com/dlclark/regexp2](https://github.com/dlclark/regexp2) |
require | patch | `v1.11.0` -> `v1.11.2` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fdlclark%2fregexp2/v1.11.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fdlclark%2fregexp2/v1.11.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fdlclark%2fregexp2/v1.11.0/v1.11.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fdlclark%2fregexp2/v1.11.0/v1.11.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [go](https://github.com/golang/go) | | patch | `1.22.4` -> `1.22.5`
|
[![age](https://developer.mend.io/api/mc/badges/age/hermit/go/1.22.5?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/hermit/go/1.22.5?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/hermit/go/1.22.4/1.22.5?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/hermit/go/1.22.4/1.22.5?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
| [watchexec](https://github.com/watchexec/watchexec) | | patch |
`2.1.1` -> `2.1.2` |
[![age](https://developer.mend.io/api/mc/badges/age/hermit/watchexec/2.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/hermit/watchexec/2.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/hermit/watchexec/2.1.1/2.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/hermit/watchexec/2.1.1/2.1.2?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.23.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.22.0...v0.23.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.22.0` or `~0.22.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Revert the recent change to avoid bundling dependencies for node
([#&#8203;3819](https://github.com/evanw/esbuild/issues/3819))

This release reverts the recent change in version 0.22.0 that made
`--packages=external` the default behavior with `--platform=node`. The
default is now back to `--packages=bundle`.

I've just been made aware that Amazon doesn't pin their dependencies in
their "AWS CDK" product, which means that whenever esbuild publishes a
new release, many people (potentially everyone?) using their SDK around
the world instantly starts using it without Amazon checking that it
works first. This change in version 0.22.0 happened to break their SDK.
I'm amazed that things haven't broken before this point. This revert
attempts to avoid these problems for Amazon's customers. Hopefully
Amazon will pin their dependencies in the future.

In addition, this is probably a sign that esbuild is used widely enough
that it now needs to switch to a more complicated release model. I may
have esbuild use a beta channel model for further development.

- Fix preserving collapsed JSX whitespace
([#&#8203;3818](https://github.com/evanw/esbuild/issues/3818))

When transformed, certain whitespace inside JSX elements is ignored
completely if it collapses to an empty string. However, the whitespace
should only be ignored if the JSX is being transformed, not if it's
being preserved. This release fixes a bug where esbuild was previously
incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is
an example:

    ```jsx
    // Original code
    <Foo>
      <Bar />
    </Foo>

    // Old output (with --jsx=preserve)
    <Foo><Bar /></Foo>;

    // New output (with --jsx=preserve)
    <Foo>
      <Bar />
    </Foo>;
    ```

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

</details>

<details>
<summary>dlclark/regexp2 (github.com/dlclark/regexp2)</summary>

###
[`v1.11.2`](https://github.com/dlclark/regexp2/compare/v1.11.1...v1.11.2)

[Compare
Source](https://github.com/dlclark/regexp2/compare/v1.11.1...v1.11.2)

###
[`v1.11.1`](https://github.com/dlclark/regexp2/compare/v1.11.0...v1.11.1)

[Compare
Source](https://github.com/dlclark/regexp2/compare/v1.11.0...v1.11.1)

</details>

<details>
<summary>golang/go (go)</summary>

###
[`v1.22.5`](https://github.com/golang/go/compare/go1.22.4...go1.22.5)

</details>

<details>
<summary>watchexec/watchexec (watchexec)</summary>

###
[`v2.1.2`](https://github.com/watchexec/watchexec/releases/tag/v2.1.2):
CLI v2.1.2

- New feature: `--watch-file`
([#&#8203;849](https://github.com/watchexec/watchexec/issues/849))
-   Fix: manpage entry in deb/rpm packagings

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 4am on Monday" (UTC),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config help](https://github.com/renovatebot/renovate/discussions) if
that's undesired.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/alecthomas/chroma).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuOSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate bot added a commit to redwoodjs/redwood that referenced this pull request Jul 20, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [esbuild](https://github.com/evanw/esbuild) | [`0.21.3` ->
`0.23.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.3/0.23.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.3/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.3/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.23.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.22.0...v0.23.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.22.0` or `~0.22.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Revert the recent change to avoid bundling dependencies for node
([#&#8203;3819](https://github.com/evanw/esbuild/issues/3819))

This release reverts the recent change in version 0.22.0 that made
`--packages=external` the default behavior with `--platform=node`. The
default is now back to `--packages=bundle`.

I've just been made aware that Amazon doesn't pin their dependencies in
their "AWS CDK" product, which means that whenever esbuild publishes a
new release, many people (potentially everyone?) using their SDK around
the world instantly starts using it without Amazon checking that it
works first. This change in version 0.22.0 happened to break their SDK.
I'm amazed that things haven't broken before this point. This revert
attempts to avoid these problems for Amazon's customers. Hopefully
Amazon will pin their dependencies in the future.

In addition, this is probably a sign that esbuild is used widely enough
that it now needs to switch to a more complicated release model. I may
have esbuild use a beta channel model for further development.

- Fix preserving collapsed JSX whitespace
([#&#8203;3818](https://github.com/evanw/esbuild/issues/3818))

When transformed, certain whitespace inside JSX elements is ignored
completely if it collapses to an empty string. However, the whitespace
should only be ignored if the JSX is being transformed, not if it's
being preserved. This release fixes a bug where esbuild was previously
incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is
an example:

    ```jsx
    // Original code
    <Foo>
      <Bar />
    </Foo>

    // Old output (with --jsx=preserve)
    <Foo><Bar /></Foo>;

    // New output (with --jsx=preserve)
    <Foo>
      <Bar />
    </Foo>;
    ```

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

###
[`v0.21.5`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0215)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.4...v0.21.5)

- Fix `Symbol.metadata` on classes without a class decorator
([#&#8203;3781](https://github.com/evanw/esbuild/issues/3781))

This release fixes a bug with esbuild's support for the [decorator
metadata
proposal](https://github.com/tc39/proposal-decorator-metadata).
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
([#&#8203;3792](https://github.com/evanw/esbuild/issues/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`:

    ```js
// 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`):

    ```js
// 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
([#&#8203;3797](https://github.com/evanw/esbuild/issues/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:

    ```ts
    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
([#&#8203;3782](https://github.com/evanw/esbuild/issues/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:

    ```json
    {
      "compilerOptions": {
        "paths": {
          "js/*": ["${configDir}/dist/js/*"]
        }
      }
    }
    ```

You can read more in [TypeScript's blog post about their upcoming 5.5
release](https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-rc/#the-configdir-template-variable-for-configuration-files).
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`
([#&#8203;3794](https://github.com/evanw/esbuild/issues/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`.

###
[`v0.21.4`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0214)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.3...v0.21.4)

- Update support for import assertions and import attributes in node
([#&#8203;3778](https://github.com/evanw/esbuild/issues/3778))

Import assertions (the `assert` keyword) have been removed from node
starting in v22.0.0. So esbuild will now strip them and generate a
warning with `--target=node22` or above:

▲ [WARNING] The "assert" keyword is not supported in the configured
target environment ("node22") [assert-to-with]

            example.mjs:1:40:
1 │ import json from "esbuild/package.json" assert { type: "json" }
                │                                         ~~~~~~
                ╵                                         with

          Did you mean to use "with" instead of "assert"?

Import attributes (the `with` keyword) have been backported to node 18
starting in v18.20.0. So esbuild will no longer strip them with
`--target=node18.N` if `N` is 20 or greater.

-   Fix `for await` transform when a label is present

This release fixes a bug where the `for await` transform, which wraps
the loop in a `try` statement, previously failed to also move the loop's
label into the `try` statement. This bug only affects code that uses
both of these features in combination. Here's an example of some
affected code:

    ```js
    // Original code
    async function test() {
      outer: for await (const x of [Promise.resolve([0, 1])]) {
        for (const y of x) if (y) break outer
        throw 'fail'
      }
    }

    // Old output (with --target=es6)
    function test() {
      return __async(this, null, function* () {
        outer: try {
for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp,
error; more = !(temp = yield iter.next()).done; more = false) {
            const x = temp.value;
            for (const y of x) if (y) break outer;
            throw "fail";
          }
        } catch (temp) {
          error = [temp];
        } finally {
          try {
            more && (temp = iter.return) && (yield temp.call(iter));
          } finally {
            if (error)
              throw error[0];
          }
        }
      });
    }

    // New output (with --target=es6)
    function test() {
      return __async(this, null, function* () {
        try {
outer: for (var iter = __forAwait([Promise.resolve([0, 1])]), more,
temp, error; more = !(temp = yield iter.next()).done; more = false) {
            const x = temp.value;
            for (const y of x) if (y) break outer;
            throw "fail";
          }
        } catch (temp) {
          error = [temp];
        } finally {
          try {
            more && (temp = iter.return) && (yield temp.call(iter));
          } finally {
            if (error)
              throw error[0];
          }
        }
      });
    }
    ```

- Do additional constant folding after cross-module enum inlining
([#&#8203;3416](https://github.com/evanw/esbuild/issues/3416),
[#&#8203;3425](https://github.com/evanw/esbuild/issues/3425))

This release adds a few more cases where esbuild does constant folding
after cross-module enum inlining.

    ```ts
    // Original code: enum.ts
    export enum Platform {
      WINDOWS = 'windows',
      MACOS = 'macos',
      LINUX = 'linux',
    }

    // Original code: main.ts
    import { Platform } from './enum';
    declare const PLATFORM: string;
    export function logPlatform() {
      if (PLATFORM == Platform.WINDOWS) console.log('Windows');
      else if (PLATFORM == Platform.MACOS) console.log('macOS');
      else if (PLATFORM == Platform.LINUX) console.log('Linux');
      else console.log('Other');
    }

// Old output (with --bundle '--define:PLATFORM="macos"' --minify
--format=esm)
function
n(){"windows"=="macos"?console.log("Windows"):"macos"=="macos"?console.log("macOS"):"linux"=="macos"?console.log("Linux"):console.log("Other")}export{n
as logPlatform};

// New output (with --bundle '--define:PLATFORM="macos"' --minify
--format=esm)
    function n(){console.log("macOS")}export{n as logPlatform};
    ```

- Pass import attributes to on-resolve plugins
([#&#8203;3384](https://github.com/evanw/esbuild/issues/3384),
[#&#8203;3639](https://github.com/evanw/esbuild/issues/3639),
[#&#8203;3646](https://github.com/evanw/esbuild/issues/3646))

With this release, on-resolve plugins will now have access to the import
attributes on the import via the `with` property of the arguments
object. This mirrors the `with` property of the arguments object that's
already passed to on-load plugins. In addition, you can now pass `with`
to the `resolve()` API call which will then forward that value on to all
relevant plugins. Here's an example of a plugin that can now be written:

    ```js
    const examplePlugin = {
      name: 'Example plugin',
      setup(build) {
        build.onResolve({ filter: /.*/ }, args => {
          if (args.with.type === 'external')
            return { external: true }
        })
      }
    }

    require('esbuild').build({
      stdin: {
        contents: `
          import foo from "./foo" with { type: "external" }
          foo()
        `,
      },
      bundle: true,
      format: 'esm',
      write: false,
      plugins: [examplePlugin],
    }).then(result => {
      console.log(result.outputFiles[0].text)
    })
    ```

- Formatting support for the `@position-try` rule
([#&#8203;3773](https://github.com/evanw/esbuild/issues/3773))

Chrome shipped this new CSS at-rule in version 125 as part of the [CSS
anchor positioning
API](https://developer.chrome.com/blog/anchor-positioning-api). With
this release, esbuild now knows to expect a declaration list inside of
the `@position-try` body block and will format it appropriately.

- Always allow internal string import and export aliases
([#&#8203;3343](https://github.com/evanw/esbuild/issues/3343))

Import and export names can be string literals in ES2022+. Previously
esbuild forbid any usage of these aliases when the target was below
ES2022. Starting with this release, esbuild will only forbid such usage
when the alias would otherwise end up in output as a string literal.
String literal aliases that are only used internally in the bundle and
are "compiled away" are no longer errors. This makes it possible to use
string literal aliases with esbuild's `inject` feature even when the
target is earlier than ES2022.

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about these
updates again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/redwoodjs/redwood).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MzEuNCIsInVwZGF0ZWRJblZlciI6IjM3LjQzMS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
portrik pushed a commit to portrik/total-firestorer that referenced this pull request Aug 7, 2024
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [esbuild](https://github.com/evanw/esbuild) | [`^0.21.5` ->
`^0.23.0`](https://renovatebot.com/diffs/npm/esbuild/0.21.5/0.23.0) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.21.5/0.23.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.23.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0230)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.22.0...v0.23.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.22.0` or `~0.22.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Revert the recent change to avoid bundling dependencies for node
([#&#8203;3819](https://github.com/evanw/esbuild/issues/3819))

This release reverts the recent change in version 0.22.0 that made
`--packages=external` the default behavior with `--platform=node`. The
default is now back to `--packages=bundle`.

I've just been made aware that Amazon doesn't pin their dependencies in
their "AWS CDK" product, which means that whenever esbuild publishes a
new release, many people (potentially everyone?) using their SDK around
the world instantly starts using it without Amazon checking that it
works first. This change in version 0.22.0 happened to break their SDK.
I'm amazed that things haven't broken before this point. This revert
attempts to avoid these problems for Amazon's customers. Hopefully
Amazon will pin their dependencies in the future.

In addition, this is probably a sign that esbuild is used widely enough
that it now needs to switch to a more complicated release model. I may
have esbuild use a beta channel model for further development.

- Fix preserving collapsed JSX whitespace
([#&#8203;3818](https://github.com/evanw/esbuild/issues/3818))

When transformed, certain whitespace inside JSX elements is ignored
completely if it collapses to an empty string. However, the whitespace
should only be ignored if the JSX is being transformed, not if it's
being preserved. This release fixes a bug where esbuild was previously
incorrectly ignoring collapsed whitespace with `--jsx=preserve`. Here is
an example:

    ```jsx
    // Original code
    <Foo>
      <Bar />
    </Foo>

    // Old output (with --jsx=preserve)
    <Foo><Bar /></Foo>;

    // New output (with --jsx=preserve)
    <Foo>
      <Bar />
    </Foo>;
    ```

###
[`v0.22.0`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0220)

[Compare
Source](https://github.com/evanw/esbuild/compare/v0.21.5...v0.22.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.21.0` or `~0.21.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

- Omit packages from bundles by default when targeting node
([#&#8203;1874](https://github.com/evanw/esbuild/issues/1874),
[#&#8203;2830](https://github.com/evanw/esbuild/issues/2830),
[#&#8203;2846](https://github.com/evanw/esbuild/issues/2846),
[#&#8203;2915](https://github.com/evanw/esbuild/issues/2915),
[#&#8203;3145](https://github.com/evanw/esbuild/issues/3145),
[#&#8203;3294](https://github.com/evanw/esbuild/issues/3294),
[#&#8203;3323](https://github.com/evanw/esbuild/issues/3323),
[#&#8203;3582](https://github.com/evanw/esbuild/issues/3582),
[#&#8203;3809](https://github.com/evanw/esbuild/issues/3809),
[#&#8203;3815](https://github.com/evanw/esbuild/issues/3815))

This breaking change is an experiment. People are commonly confused when
using esbuild to bundle code for node (i.e. for `--platform=node`)
because some packages may not be intended for bundlers, and may use
node-specific features that don't work with a bundler. Even though
esbuild's "getting started" instructions say to use
`--packages=external` to work around this problem, many people don't
read the documentation and don't do this, and are then confused when it
doesn't work. So arguably this is a bad default behavior for esbuild to
have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by
default when the platform is `node` (i.e. the previous behavior of
`--packages=external` is now the default in this case). *Note that your
dependencies must now be present on the file system when your bundle is
run.* If you don't want this behavior, you can do `--packages=bundle` to
allow packages to be included in the bundle (i.e. the previous default
behavior). Note that `--packages=bundle` doesn't mean all packages are
bundled, just that packages are allowed to be bundled. You can still
exclude individual packages from the bundle using `--external:` even
when `--packages=bundle` is present.

The `--packages=` setting considers all import paths that "look like"
package imports in the original source code to be package imports.
Specifically import paths that don't start with a path segment of `/` or
`.` or `..` are considered to be package imports. The only two
exceptions to this rule are [subpath
imports](https://nodejs.org/api/packages.html#subpath-imports) (which
start with a `#` character) and TypeScript path remappings via `paths`
and/or `baseUrl` in `tsconfig.json` (which are applied first).

- Drop support for older platforms
([#&#8203;3802](https://github.com/evanw/esbuild/issues/3802))

    This release drops support for the following operating systems:

    -   Windows 7
    -   Windows 8
    -   Windows Server 2008
    -   Windows Server 2012

This is because the Go programming language dropped support for these
operating system versions in [Go
1.21](https://go.dev/doc/go1.21#windows), and this release updates
esbuild from Go 1.20 to Go 1.22.

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.21). That might look something like this:

        git clone https://github.com/evanw/esbuild.git
        cd esbuild
        go build ./cmd/esbuild
        ./esbuild.exe --version

In addition, this release increases the minimum required node version
for esbuild's JavaScript API from node 12 to node 18. Node 18 is the
oldest version of node that is still being supported (see node's
[release schedule](https://nodejs.org/en/about/previous-releases) for
more information). This increase is because of an incompatibility
between the JavaScript that the Go compiler generates for the
`esbuild-wasm` package and versions of node before node 17.4
(specifically the `crypto.getRandomValues` function).

-   Update `await using` behavior to match TypeScript

TypeScript 5.5 subtly changes the way `await using` behaves. This
release updates esbuild to match these changes in TypeScript. You can
read more about these changes in
[microsoft/TypeScript#58624](https://github.com/microsoft/TypeScript/pull/58624).

-   Allow `es2024` as a target environment

The ECMAScript 2024 specification was just approved, so it has been
added to esbuild as a possible compilation target. You can read more
about the features that it adds here:
<https://2ality.com/2024/06/ecmascript-2024.html>. The only addition
that's relevant for esbuild is the regular expression `/v` flag. With
`--target=es2024`, regular expressions that use the `/v` flag will now
be passed through untransformed instead of being transformed into a call
to `new RegExp`.

- Publish binaries for OpenBSD on 64-bit ARM
([#&#8203;3665](https://github.com/evanw/esbuild/issues/3665),
[#&#8203;3674](https://github.com/evanw/esbuild/pull/3674))

With this release, you should now be able to install the `esbuild` npm
package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1
chip.

This was contributed by
[@&#8203;ikmckenz](https://github.com/ikmckenz).

- Publish binaries for WASI (WebAssembly System Interface) preview 1
([#&#8203;3300](https://github.com/evanw/esbuild/issues/3300),
[#&#8203;3779](https://github.com/evanw/esbuild/pull/3779))

The upcoming WASI (WebAssembly System Interface) standard is going to be
a way to run WebAssembly outside of a JavaScript host environment. In
this scenario you only need a `.wasm` file without any supporting
JavaScript code. Instead of JavaScript providing the APIs for the host
environment, the WASI standard specifies a "system interface" that
WebAssembly code can access directly (e.g. for file system access).

Development versions of the WASI specification are being released using
preview numbers. The people behind WASI are currently working on preview
2 but the Go compiler has [released support for preview
1](https://go.dev/blog/wasi), which from what I understand is now
considered an unsupported legacy release. However, some people have
requested that esbuild publish binary executables that support WASI
preview 1 so they can experiment with them.

This release publishes esbuild precompiled for WASI preview 1 to the
`@esbuild/wasi-preview1` package on npm (specifically the file
`@esbuild/wasi-preview1/esbuild.wasm`). This binary executable has not
been tested and won't be officially supported, as it's for an old
preview release of a specification that has since moved in another
direction. If it works for you, great! If not, then you'll likely have
to wait for the ecosystem to evolve before using esbuild with WASI. For
example, it sounds like perhaps WASI preview 1 doesn't include support
for opening network sockets so esbuild's local development server is
unlikely to work with WASI preview 1.

- Warn about `onResolve` plugins not setting a path
([#&#8203;3790](https://github.com/evanw/esbuild/issues/3790))

Plugins that return values from `onResolve` without resolving the path
(i.e. without setting either `path` or `external: true`) will now cause
a warning. This is because esbuild only uses return values from
`onResolve` if it successfully resolves the path, and it's not good for
invalid input to be silently ignored.

- Add a new Go API for running the CLI with plugins
([#&#8203;3539](https://github.com/evanw/esbuild/pull/3539))

With esbuild's Go API, you can now call `cli.RunWithPlugins(args,
plugins)` to pass an array of esbuild plugins to be used during the
build process. This allows you to create a CLI that behaves similarly to
esbuild's CLI but with additional Go plugins enabled.

This was contributed by [@&#8203;edewit](https://github.com/edewit).

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View the
[repository job
log](https://developer.mend.io/github/portrik/total-firestorer).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4yMC4xIiwidXBkYXRlZEluVmVyIjoiMzguMjAuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Author: Team For Milestone Bug PRs that fix a bug with a specific milestone
Projects
None yet
3 participants