fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@fastify/swagger	8.2.0 -> 8.2.1
@types/node (source)	18.11.11 -> 18.11.13
@typescript-eslint/eslint-plugin	5.45.1 -> 5.46.1
@typescript-eslint/parser	5.45.1 -> 5.46.1
esbuild	0.16.1 -> 0.16.4
typescript (source)	4.9.3 -> 4.9.4

---

Release Notes

fastify/fastify-swagger

v8.2.1

Compare Source

📚 PR:

• chore(deps-dev): bump tsd from 0.24.1 to 0.25.0 (#​699)
• fix examples in json schema (#​702)

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.46.1

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.46.0

Compare Source

Bug Fixes

• eslint-plugin: [ban-types] update message to suggest object instead of Record<string, unknown> (#​6079) (d91a5fc)

Features

• eslint-plugin: [prefer-nullish-coalescing] logic and test for strict null checks (#​6174) (8a91cbd)

5.45.1 (2022-12-05)

Bug Fixes

• eslint-plugin: [keyword-spacing] unexpected space before/after in import type (#​6095) (98caa92)
• eslint-plugin: [no-shadow] add call and method signatures to ignoreFunctionTypeParameterNameValueShadow (#​6129) (9d58b6b)
• eslint-plugin: [prefer-optional-chain] collect MetaProperty type (#​6083) (d7114d3)
• eslint-plugin: [sort-type-constituents, sort-type-union-intersection-members] handle some required parentheses cases in the fixer (#​6118) (5d49d5d)

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.46.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.46.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

5.45.1 (2022-12-05)

Bug Fixes

• parser: remove the jsx option requirement for automatic jsx pragma resolution (#​6134) (e777f5e)

evanw/esbuild

v0.16.4

Compare Source

• Fix binary downloads from the @esbuild/ scope for Deno (#​2729)

  Version 0.16.0 of esbuild moved esbuild's binary executables into npm packages under the @esbuild/ scope, which accidentally broke the binary downloader script for Deno. This release fixes this script so it should now be possible to use esbuild version 0.16.4+ with Deno.

v0.16.3

Compare Source

• Fix a hang with the JS API in certain cases (#​2727)

  A change that was made in version 0.15.13 accidentally introduced a case when using esbuild's JS API could cause the node process to fail to exit. The change broke esbuild's watchdog timer, which detects if the parent process no longer exists and then automatically exits esbuild. This hang happened when you ran node as a child process with the stderr stream set to pipe instead of inherit, in the child process you call esbuild's JS API and pass incremental: true but do not call dispose() on the returned rebuild object, and then call process.exit(). In that case the parent node process was still waiting for the esbuild process that was created by the child node process to exit. The change made in version 0.15.13 was trying to avoid using Go's sync.WaitGroup API incorrectly because the API is not thread-safe. Instead of doing this, I have now reverted that change and implemented a thread-safe version of the sync.WaitGroup API for esbuild to use instead.

v0.16.2

Compare Source

• Fix process.env.NODE_ENV substitution when transforming (#​2718)

  Version 0.16.0 introduced an unintentional regression that caused process.env.NODE_ENV to be automatically substituted with either "development" or "production" when using esbuild's transform API. This substitution is a necessary feature of esbuild's build API because the React framework crashes when you bundle it without doing this. But the transform API is typically used as part of a larger build pipeline so the benefit of esbuild doing this automatically is not as clear, and esbuild previously didn't do this.

  However, version 0.16.0 switched the default value of the platform setting for the transform API from neutral to browser, both to align it with esbuild's documentation (which says browser is the default value) and because escaping the </script> character sequence is now tied to the browser platform (see the release notes for version 0.16.0 for details). That accidentally enabled automatic substitution of process.env.NODE_ENV because esbuild always did that for code meant for the browser. To fix this regression, esbuild will now only automatically substitute process.env.NODE_ENV when using the build API.

• Prevent define from substituting constants into assignment position (#​2719)

  The define feature lets you replace certain expressions with constants. For example, you could use it to replace references to the global property reference window.DEBUG with false at compile time, which can then potentially help esbuild remove unused code from your bundle. It's similar to DefinePlugin in Webpack.

  However, if you write code such as window.DEBUG = true and then defined window.DEBUG to false, esbuild previously generated the output false = true which is a syntax error in JavaScript. This behavior is not typically a problem because it doesn't make sense to substitute window.DEBUG with a constant if its value changes at run-time (Webpack's DefinePlugin also generates false = true in this case). But it can be alarming to have esbuild generate code with a syntax error.

  So with this release, esbuild will no longer substitute define constants into assignment position to avoid generating code with a syntax error. Instead esbuild will generate a warning, which currently looks like this:

  ▲ [WARNING] Suspicious assignment to defined constant "window.DEBUG" [assign-to-define]
  
      example.js:1:0:
        1 │ window.DEBUG = true
          ╵ ~~~~~~~~~~~~
  
    The expression "window.DEBUG" has been configured to be replaced with a constant using the
    "define" feature. If this expression is supposed to be a compile-time constant, then it doesn't
    make sense to assign to it here. Or if this expression is supposed to change at run-time, this
    "define" substitution should be removed.
  

• Fix a regression with npm install --no-optional (#​2720)

  Normally when you install esbuild with npm install, npm itself is the tool that downloads the correct binary executable for the current platform. This happens because of how esbuild's primary package uses npm's optionalDependencies feature. However, if you deliberately disable this with npm install --no-optional then esbuild's install script will attempt to repair the installation by manually downloading and extracting the binary executable from the package that was supposed to be installed.

  The change in version 0.16.0 to move esbuild's nested packages into the @esbuild/ scope unintentionally broke this logic because of how npm's URL structure is different for scoped packages vs. normal packages. It was actually already broken for a few platforms earlier because esbuild already had packages for some platforms in the @esbuild/ scope, but I didn't discover this then because esbuild's integration tests aren't run on all platforms. Anyway, this release contains some changes to the install script that should hopefully get this scenario working again.

Microsoft/TypeScript

v4.9.4: TypeScript 4.9.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v4.9.4.

Downloads are available on:

• npm
• NuGet package

Changes:

• e286821 Bump version to 4.9.4 and LKG.
• eb5419f Cherry-pick #​51704 to release 4.9 (#​51712)
• b4d382b Cherry-pick changes for narrowing to tagged literal types.
• e7a02f4 Port of #​51626 and #​51689 to release-4.9 (#​51627)
• 1727912 Cherry-pick fix around visitEachChild to release-4.9. (#​51544)

This list of changes was auto generated.

---

Configuration

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

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.