chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@azure/functions	4.5.0 -> 4.6.0
@azure/static-web-apps-cli	1.1.9 -> 1.1.10
@cloudflare/workers-types	4.20240620.0 -> 4.20241106.0
@types/eslint (source)	8.56.10 -> 8.56.12
@types/node (source)	20.14.8 -> 20.17.6
@typescript-eslint/eslint-plugin (source)	7.13.1 -> 7.18.0
@typescript-eslint/parser (source)	7.13.1 -> 7.18.0
eslint (source)	8.57.0 -> 8.57.1
npm-run-all2	6.2.0 -> 6.2.6
pnpm (source)	9.4.0 -> 9.12.3
prettier (source)	3.3.2 -> 3.3.3
typescript (source)	5.5.2 -> 5.6.3
undici (source)	6.19.2 -> 6.20.1
vite (source)	5.3.1 -> 5.4.10
wrangler (source)	3.61.0 -> 3.86.0

---

Release Notes

Azure/azure-functions-nodejs-library (@​azure/functions)

v4.6.0

Compare Source

Fixed

• Bump cookie from 0.6.0 to 0.7.0 by @​dependabot in https://github.com/Azure/azure-functions-nodejs-library/pull/310

Full Changelog: Azure/azure-functions-nodejs-library@v4.5.1...v4.6.0

v4.5.1

Compare Source

Fixed

• Fixed undefined HTTP params when streaming is enabled #​285

azure/static-web-apps-cli (@​azure/static-web-apps-cli)

v1.1.10

Compare Source

What's Changed

• fix(cli): Fix VuePress swa init and start by @​Timothyw0 in https://github.com/Azure/static-web-apps-cli/pull/852
• Remove the second server.listen so that it also works with Node 20.13 by @​yamachu in https://github.com/Azure/static-web-apps-cli/pull/841
• chore: prep release 1.1.10 by @​Timothyw0 in https://github.com/Azure/static-web-apps-cli/pull/854
• docs: Make the recommended install the main one by @​janpieterz in https://github.com/Azure/static-web-apps-cli/pull/637

New Contributors

• @​janpieterz made their first contribution in https://github.com/Azure/static-web-apps-cli/pull/637

Full Changelog: Azure/static-web-apps-cli@v1.1.9...v1.1.10

cloudflare/workerd (@​cloudflare/workers-types)

v4.20241106.0

Compare Source

v4.20241022.0

Compare Source

v4.20241018.0

Compare Source

v4.20241011.0

Compare Source

v4.20241004.0

Compare Source

v4.20240925.0

Compare Source

v4.20240924.0

Compare Source

v4.20240919.0

Compare Source

v4.20240909.0

Compare Source

v4.20240903.0

Compare Source

v4.20240821.1

Compare Source

v4.20240815.0

Compare Source

v4.20240806.0

Compare Source

v4.20240729.0

Compare Source

v4.20240725.0

Compare Source

v4.20240722.0

Compare Source

v4.20240718.0

Compare Source

v4.20240712.0

Compare Source

v4.20240701.0

Compare Source

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

v7.18.0

Compare Source

🩹 Fixes

• eslint-plugin: [no-unnecessary-type-assertion] prevent runtime error when asserting a variable declared in default TS lib

• eslint-plugin: [unbound-method] report on destructuring in function parameters

• eslint-plugin: [no-duplicate-type-constituents] shouldn't report on error types

• eslint-plugin: [strict-boolean-expressions] support branded booleans

❤️ Thank You

• auvred
• Oliver Salzburg
• Vinccool96
• Yukihiro Hasegawa

You can read about our versioning strategy and releases on our website.

v7.17.0

Compare Source

🚀 Features

• eslint-plugin: backport no-unsafe-function type, no-wrapper-object-types from v8 to v7

• eslint-plugin: [return-await] add option to report in error-handling scenarios only, and deprecate "never"

🩹 Fixes

• eslint-plugin: [no-floating-promises] check top-level type assertions (and more)

• eslint-plugin: [strict-boolean-expressions] consider assertion function argument a boolean context

• eslint-plugin: [no-unnecessary-condition] false positive on optional private field

❤️ Thank You

• Armano
• Josh Goldberg ✨
• Kirk Waiblinger
• StyleShit

You can read about our versioning strategy and releases on our website.

v7.16.1

Compare Source

🩹 Fixes

• eslint-plugin: [no-unnecessary-type-parameters] descend into all parts of mapped types in no-unnecessary-type-parameters

❤️ Thank You

• Dan Vanderkam

You can read about our versioning strategy and releases on our website.

v7.16.0

Compare Source

🚀 Features

• rule-tester: stricter rule test validations

• eslint-plugin: [no-unnecessary-parameter-property-assignment] add new rule

• eslint-plugin: add support for nested namespaces to unsafe-member-access

• eslint-plugin: [no-floating-promises] add checkThenables option

🩹 Fixes

• deps: update dependency @​eslint-community/regexpp to v4.11.0

• eslint-plugin: [no-floating-promises] add suggestions to tests from #​9263 checkThenables

• website: react key error on internal pages of website

• eslint-plugin: [restrict-template-expressions] don't report tuples if allowArray option is enabled

❤️ Thank You

• Abraham Guo
• auvred
• Josh Goldberg ✨
• Juan Sanchez
• Vinccool96
• YeonJuan
• Yukihiro Hasegawa

You can read about our versioning strategy and releases on our website.

v7.15.0

Compare Source

🚀 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 and releases on our website.

v7.14.1

Compare Source

🩹 Fixes

• eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types

• eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens

❤️ Thank You

• Jake Bailey

You can read about our versioning strategy and releases on our website.

v7.14.0

Compare Source

🚀 Features

• support TypeScript 5.5

🩹 Fixes

• eslint-plugin: [no-extraneous-class] handle abstract members

• eslint-plugin: [prefer-nullish-coalescing] handle intersected primitive types

• eslint-plugin: [no-invalid-this] support AccessorProperty

❤️ Thank You

• Brad Zacher
• cm-ayf
• Jake Bailey
• James Zhan
• Joshua Chen
• yoshi2no

You can read about our versioning strategy and releases on our website.

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

v7.18.0

Compare Source

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 and releases on our website.

v7.17.0

Compare Source

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 and releases on our website.

v7.16.1

Compare Source

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 and releases on our website.

v7.16.0

Compare Source

🩹 Fixes

• deps: update dependency @​eslint-community/regexpp to v4.11.0

• website: react key error on internal pages of website

❤️ Thank You

• Abraham Guo
• auvred
• Josh Goldberg ✨
• Juan Sanchez
• Vinccool96
• YeonJuan
• Yukihiro Hasegawa

You can read about our versioning strategy and releases on our website.

v7.15.0

Compare Source

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 and releases on our website.

v7.14.1

Compare Source

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 and releases on our website.

v7.14.0

Compare Source

🚀 Features

• support TypeScript 5.5

❤️ Thank You

• Brad Zacher
• cm-ayf
• Jake Bailey
• James Zhan
• Joshua Chen
• yoshi2no

You can read about our versioning strategy and releases on our website.

eslint/eslint (eslint)

v8.57.1

Compare Source

bcomnes/npm-run-all2 (npm-run-all2)

v6.2.6

Compare Source

Commits

• Prevent a throw when looking up undefined results d928f9a

v6.2.5

Compare Source

v6.2.4

Compare Source

Merged

• Switch to JS-based which command #154

Fixed

• Switch to JS-based which command #153

v6.2.3

Compare Source

Commits

• Merge pull request #​151 from bcomnes/fix-pnpm-agian c43fa2b
• Avoid passing config fields as flags for pnpm dc2d7da

v6.2.2

Compare Source

Commits

• Revert "Compatibility: npm, yarn and pnpm run scripts" fc35f0d

v6.2.1

Compare Source

Merged

• Compatibility: npm, yarn and pnpm run scripts #143
• Use neostandard + add more static code analysis #142
• Upgrade: Bump c8 from 9.1.0 to 10.0.0 #141
• Upgrade: Bump p-queue from 7.4.1 to 8.0.1 #138

pnpm/pnpm (pnpm)

v9.12.3

Compare Source

Patch Changes

• Don't purge node_modules, when typing "n" in the prompt that asks whether to remove node_modules before installation #​8655.
• Fix a bug causing pnpm to infinitely spawn itself when manage-package-manager-versions=true is set and the .tools directory is corrupt.
• Use crypto.hash, when available, for improved performance #​8629.
• Fixed a race condition in temporary file creation in the store by including worker thread ID in filename. Previously, multiple worker threads could attempt to use the same temporary file. Temporary files now include both process ID and thread ID for uniqueness #​8703.
• All commands should read settings from the package.json at the root of the workspace #​8667.
• When manage-package-manager-versions is set to true, errors spawning a self-managed version of pnpm will now be shown (instead of being silent).
• Pass the find command to npm, it is an alias for npm search

v9.12.2

Compare Source

Patch Changes

• When checking whether a file in the store has executable permissions, the new approach checks if at least one of the executable bits (owner, group, and others) is set to 1. Previously, a file was incorrectly considered executable only when all the executable bits were set to 1. This fix ensures that files with any executable permission, regardless of the user class, are now correctly identified as executable #​8546.

v9.12.1

Compare Source

Patch Changes

• pnpm update --latest should not update the automatically installed peer dependencies #​6657.
• pnpm publish should be able to publish from a local tarball #​7950.
• The pnpx command should work correctly on Windows, when pnpm is installed via the standalone installation script #​8608.
• Prevent EBUSY errors caused by creating symlinks in parallel dlx processes #​8604.
• Fix maximum call stack size exceeded error related to circular workspace dependencies #​8599.

v9.12.0

Compare Source

Minor Changes

• Fix peer dependency resolution dead lock #​8570. This change might change some of the keys in the snapshots field inside pnpm-lock.yaml but it should happen very rarely.

• pnpm outdated command supports now a --sort-by=name option for sorting outdated dependencies by package name #​8523.

• Added the ability for overrides to remove dependencies by specifying "-" as the field value #​8572. For example, to remove lodash from the dependencies, use this configuration in package.json:

  {
    "pnpm": {
      "overrides": {
        "lodash": "-"
      }
    }
  }

Patch Changes

• Fixed an issue where pnpm list --json pkg showed "private": false for a private package #​8519.
• Packages with libc that differ from pnpm.supportedArchitectures.libc are not downloaded #​7362.
• Prevent ENOENT errors caused by running store prune in parallel #​8586.
• Add issues alias to pnpm bugs #​8596.

v9.11.0

Compare Source

Minor Changes

• Experimental: added pnpm cache commands for inspecting the metadata cache #​8512.

Patch Changes

• Fix a regression in which pnpm deploy with node-linker=hoisted produces an empty node_modules directory #​6682.
• Don't print a warning when linking packages globally #​4761.
• pnpm deploy should work in workspace with shared-workspace-lockfile=false #​8475.

v9.10.0

Compare Source

Minor Changes

• Support for a new CLI flag, --exclude-peers, added to the list and why commands. When --exclude-peers is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #​8506.

• Added a new setting to package.json at pnpm.auditConfig.ignoreGhsas for ignoring vulnerabilities by their GHSA code #​6838.

  For instance:

  {
    "pnpm": {
      "auditConfig": {
        "ignoreGhsas": [
          "GHSA-42xw-2xvc-qx8m",
          "GHSA-4w2v-q235-vp99",
          "GHSA-cph5-m8f7-6c5x",
          "GHSA-vh95-rmgr-6w4m"
        ]
      }
    }
  }

Patch Changes

• Throw an exception if pnpm switches to the same version of itself.
• Reduce memory usage during peer dependencies resolution.

v9.9.0

Compare Source

Minor Changes

• Minor breaking change. This change might result in resolving your peer dependencies slightly differently but we don't expect it to introduce issues.

  We had to optimize how we resolve peer dependencies in order to fix some infinite loops and out-of-memory errors during peer dependencies resolution.

  When a peer dependency is a prod dependency somewhere in the dependency graph (with the same version), pnpm will resolve the peers of that peer dependency in the same way across the subgraph.

  For example, we have react-dom in the peer deps of the form and button packages. card has react-dom and react as regular dependencies and card is a dependency of form.

  These are the direct dependencies of our example project:

  form
  react@16
  react-dom@16
  

  These are the dependencies of card:

  button
  react@17
  react-dom@16
  

  When resolving peers, pnpm will not re-resolve react-dom for card, even though card shadows react@16 from the root with react@17. So, all 3 packages (form, card, and button) will use react-dom@16, which in turn uses react@16. form will use react@16, while card and button will use react@17.

  Before this optimization react-dom@16 was duplicated for the card, so that card and button would use a react-dom@16 instance that uses react@17.

  Before the change:

  form
  -> react-dom@16(react@16)
  -> react@16
  card
  -> react-dom@16(react@17)
  -> react@17
  button
  -> react-dom@16(react@17)
  -> react@17
  

  After the change

  form
  -> react-dom@16(react@16)
  -> react@16
  card
  -> react-dom@16(react@16)
  -> react@17
  button
  -> react-dom@16(react@16)
  -> react@17
  

Patch Changes

• pnpm deploy should write the node_modules/.modules.yaml to the node_modules directory within the deploy directory #​7731.
• Don't override a symlink in node_modules if it already points to the right location pnpm/symlink-dir#54.

v9.8.0

Compare Source

Minor Changes

• Added a new command for upgrading pnpm itself when it isn't managed by Corepack: pnpm self-update. This command will work, when pnpm was installed via the standalone script from the pnpm installation page #​8424.

  When executed in a project that has a packageManager field in its package.json file, pnpm will update its version in the packageManager field.

Patch Changes

• CLI tools installed in the root of the workspace should be added to the PATH, when running scripts and use-node-version is set.

• pnpm setup should never switch to another version of pnpm.

  This fixes installation with the standalone script from a directory that has a package.json with the packageManager field. pnpm was installing the version of pnpm specified in the packageManager field due to this issue.

• Ignore non-string value in the os, cpu, libc fields, which checking optional dependencies #​8431.

• Remember the state of edit dir, allow running pnpm patch-commit the second time without having to re-run pnpm patch.

v9.7.1

Compare Source

Patch Changes

• Fixed passing public-hoist-pattern and hoist-pattern via env variables #​8339.
• pnpm setup no longer creates Batch/Powershell scripts on Linux and macOS #​8418.
• When dlx uses cache, use the real directory path not the symlink to the cache #​8421.
• pnpm exec now supports executionEnv #​8356.
• Remove warnings for non-root pnpm field, add warnings for non-root pnpm subfields that aren't executionEnv #​8143.
• Replace semver in "peerDependency" with workspace protocol #​8355.
• Fix a bug in patch-commit in which relative path is rejected #​8405.
• Update Node.js in @pnpm/exe to v20.

v9.7.0

Compare Source

Minor Changes

• Added pnpm version management to pnpm. If the manage-package-manager-versions setting is set to true, pnpm will switch to the version specified in the packageManager field of package.json #​8363. This is the same field used by Corepack. Example:

  {
    "packageManager": "[email protected]"
  }

• Added the ability to apply patch to all versions:
  If the key of pnpm.patchedDependencies is a package name without a version (e.g. pkg), pnpm will attempt to apply the patch to all versions of
  the package. Failures will be skipped.
  If it is a package name and an exact version (e.g. [email protected]), pnpm will attempt to apply the patch to that exact version only. Failures will
  cause pnpm to fail.

  If there's only one version of pkg installed, pnpm patch pkg and subsequent pnpm patch-commit $edit_dir will create an entry named pkg in
  pnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions of pkg in the future.

  If there are multiple versions of pkg installed, pnpm patch pkg will ask which version to edit and whether to attempt to apply the patch to all.
  If the user chooses to apply the patch to all, pnpm patch-commit $edit_dir would create a pkg entry in pnpm.patchedDependencies.
  If the user chooses not to apply the patch to all, pnpm patch-commit $edit_dir would create a [email protected] entry in pnpm.patchedDependencies with
  x.y.z being the version the user chose to edit.

  If the user runs pnpm patch [email protected] with x.y.z being the exact version of pkg that has been installed, pnpm patch-commit $edit_dir will always
  create a [email protected] entry in pnpm.patchedDependencies.

• Change the default edit dir location when running pnpm patch from a temporary directory to node_modules/.pnpm_patches/pkg[@​version] to allow the code editor to open the edit dir in the same file tree as the main project.

• Substitute environment variables in config keys #​6679.

Patch Changes

• pnpm install should run node-gyp rebuild if the project has a binding.gyp file even if the project doesn't have an install script #​8293.
• Print warnings to stderr #​8342.
• Peer dependencies of optional peer dependencies should be automatically installed #​8323.

v9.6.0

Compare Source

Minor Changes

• Support specifying node version (via pnpm.executionEnv.nodeVersion in package.json) for running lifecycle scripts per each package in a workspace #​6720.
• Overrides now support the catalogs: protocol #​8303.

Patch Changes

• The pnpm deploy command now supports the catalog: protocol #​8298.
• The pnpm outdated command now supports the catalog: protocol #​8304.
• Correct the error message when trying to run pnpm patch without node_modules/.modules.yaml #​8257.
• Silent reporting fixed with the pnpm exec command #​7608.
• Add registries information to the calculation of dlx cache hash #​8299.

v9.5.0

Compare Source

Minor Changes

• Added support for catalogs 8122.

  Catalogs may be declared in the pnpm-workspace.yaml file. For example:

prettier/prettier (prettier)

v3.3.3

Compare Source

diff

Add parentheses for nullish coalescing in ternary (#​16391 by @​cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);

Add parentheses for decorator expressions (#​16458 by @​y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@​(foo`tagged template`)
class X {}

// Prettier 3.3.2
@​foo`tagged template`
class X {}

// Prettier 3.3.3
@​(foo`tagged template`)
class X {}

Support @let declaration syntax (#​16474 by @​sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

@​let name = 'Frodo';

<h1>Dashboard for {{name}}</h1>
Hello, {{name}}

For more details, please refer to the excellent blog post by the Angular Team: Introducing @​let in Angular.

We also appreciate the Angular Team for kindly answering our questions to implement this feature.

microsoft/TypeScript (typescript)

v5.6.3

Compare Source

v5.6.2

Compare Source

v5.5.4: TypeScript 5.5.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 v5.5.4 (Stable).
• fixed issues query for TypeScript v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package (soon!)

v5.5.3: TypeScript 5.5.3

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 v5.5.3 (Stable).
• fixed issues query for TypeScript v5.5.2 (Stable).
• fixed issues query for TypeScript v5.5.1 (RC).
• fixed issues query for TypeScript v5.5.0 (Beta).

Downloads are available on:

• npm
• NuGet package

nodejs/undici (undici)

v6.20.1

Compare Source

v6.20.0

Compare Source

What's Changed

• Remove patched dom types (v6.x branch) by @​eXhumer in https://github.com/nodejs/undici/pull/3531
• docs(Backport v6.x): Fix signature of RetryHandler by @​github-actions in https://github.com/nodejs/undici/pull/3594
• deps(dev): update @​types/node by @​metcoder95 in https://github.com/nodejs/undici/pull/3618
• fix: throw on retry when payload is consume by downstream by @​github-actions in https://github.com/nodejs/undici/pull/3596
• feat(Backport v6.x): move throwOnError to interceptor by @​github-actions in https://github.com/nodejs/undici/pull/3595
• [Backport v6.x] fix: reduce memory usage in client-h1 by @​github-actions in https://github.com/nodejs/undici/pull/3672
• [Backport v6.x] fix: refactor fast timers, fix UND_ERR_CONNECT_T

---

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.

👻 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 was generated by Mend Renovate. View the repository job log.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud