chore(deps): update all non-major dependencies

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	`^20.11.7` -> `^20.11.10`
esbuild	`^0.19.12` -> `^0.20.0`
pnpm (source)	`8.14.3` -> `8.15.0`

Release Notes

evanw/esbuild (esbuild)

### [`v0.20.0`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0200) [Compare Source](https://togithub.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 ([#3609](https://togithub.com/evanw/esbuild/issues/3609), [#3611](https://togithub.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` ([#3341](https://togithub.com/evanw/esbuild/issues/3341), [#3608](https://togithub.com/evanw/esbuild/issues/3608)) In [version 0.18.0](https://togithub.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.

pnpm/pnpm (pnpm)

### [`v8.15.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.15.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.14.3...v8.15.0) #### Minor Changes - When the license field does not exist in `package.json` but a license file exists, try to match and extract the license name [#7530](https://togithub.com/pnpm/pnpm/pull/7530). #### Patch Changes - Running `pnpm update -r --latest` will no longer downgrade prerelease dependencies [#7436](https://togithub.com/pnpm/pnpm/issues/7436). - `--aggregate-output` should work on scripts executed from the same project [#7556](https://togithub.com/pnpm/pnpm/issues/7556). - Prefer hard links over reflinks on Windows as they perform better [#7564](https://togithub.com/pnpm/pnpm/pull/7564). - Reduce the length of the side-effects cache key. Instead of saving a stringified object composed from the dependency versions of the package, use the hash calculated from the said object [#7563](https://togithub.com/pnpm/pnpm/pull/7563). - Throw an error if `pnpm update --latest` runs with arguments containing versions specs. For instance, `pnpm update --latest foo@next` is not allowed [#7567](https://togithub.com/pnpm/pnpm/pull/7567). - Don't fail in Windows CoW if the file already exists [#7554](https://togithub.com/pnpm/pnpm/issues/7554). #### Platinum Sponsors