chore(deps-dev): bump pnpm from 9.15.2 to 10.4.0

[dependabot]

Bumps pnpm from 9.15.2 to 10.4.0.

Release notes

Sourced from pnpm's releases.

pnpm 10.4

See breaking changes in v10

Minor Changes

• pnpm approve-builds --global works now for allowing dependencies of globally installed packages to run postinstall scripts.

• The pnpm add command now supports a new flag, --allow-build, which allows building the specified dependencies. For instance, if you want to install a package called bundle that has esbuild as a dependency and want to allow esbuild to run postinstall scripts, you can run:

  pnpm --allow-build=esbuild add bundle
  

  This will run esbuild's postinstall script and also add it to the pnpm.onlyBuiltDependencies field of package.json. So, esbuild will always be allowed to run its scripts in the future.

  Related PR: #9086.

Patch Changes

• pnpm approve-builds should work after two consecutive pnpm install runs #9083.
• Fix instruction for updating pnpm with corepack #9101.
• The pnpm version specified by packageManager cannot start with v.

Platinum Sponsors

Gold Sponsors

... (truncated)

Changelog

Sourced from pnpm's changelog.

10.4.0

Minor Changes

• pnpm approve-builds --global works now for allowing dependencies of globally installed packages to run postinstall scripts.

• The pnpm add command now supports a new flag, --allow-build, which allows building the specified dependencies. For instance, if you want to install a package called bundle that has esbuild as a dependency and want to allow esbuild to run postinstall scripts, you can run:

  pnpm --allow-build=esbuild add bundle
  

  This will run esbuild's postinstall script and also add it to the pnpm.onlyBuiltDependencies field of package.json. So, esbuild will always be allowed to run its scripts in the future.

  Related PR: #9086.

• The pnpm init command adds a packageManager field with the current version of pnpm CLI #9069. To disable this behaviour, set the init-package-manager setting to false.

Patch Changes

• pnpm approve-builds should work after two consecutive pnpm install runs #9083.
• Fix instruction for updating pnpm with corepack #9101.
• The pnpm version specified by packageManager cannot start with v.

10.3.0

Minor Changes

• Added a new setting called strict-dep-builds. When enabled, the installation will exit with a non-zero exit code if any dependencies have unreviewed build scripts (aka postinstall scripts) #9071.

Patch Changes

• Fix a false negative of verify-deps-before-run after pnpm install --production|--no-optional #9019.
• Print the warning about blocked installation scripts at the end of the installation output and make it more prominent.

10.2.1

Patch Changes

• Don't read a package from side-effects cache if it isn't allowed to be built #9042.
• pnpm approve-builds should work, when executed from a subdirectory of a workspace #9042.
• pnpm deploy --legacy should work without injected dependencies.
• Add information about how to deploy without "injected dependencies" to the "pnpm deploy" error message.

10.2.0

Minor Changes

• Packages executed via pnpm dlx and pnpm create are allowed to be built (run postinstall scripts) by default.

  If the packages executed by dlx or create have dependencies that have to be built, they should be listed via the --allow-build flag. For instance, if you want to run a package called bundle that has esbuild in dependencies and want to allow esbuild to run postinstall scripts, run:

... (truncated)

Commits

• 2a6b51f chore(release): 10.4.0
• 91d46ee feat: add --allow-build=\<pkg> to add command (#9086)
• 31d15ff chore: pass all env variables to pnpm CLI, when running pd
• a5b36b7 fix: don't remove ignored builds list on repeat install (#9083)
• 4304d8e fix: packageManager specified version should not start with v (#9057)
• 1dc2804 chore(release): 10.3.0
• f6006f2 feat: add an option to fail on unapproved dependency builds (#9071)
• e209a35 chore: override request with postmap-request
• 265946b fix: verify-deps-before-run after install --prod|--no-optional (#9055)
• d40dfeb chore(release): 10.2.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #187.