pnpm's settings

pnpm 12 reads project settings from here, not from .npmrc or package.json. It's a settings file, not a workspace. The same settings belong in every repository, so a change here is a change to the rules.

pnpm holds back a version for a day after it's published, so a bad release can be caught before it's installed. That default is kept, and our own packages skip the wait, since each reaches npm only after the owner approves it with 2FA. The scope, not a version, is named, so a release needs no change here.

minimumReleaseAgeExclude:
  - "@amitkaps/*"

Dependencies allowed to run install scripts. Both are native binaries: esbuild for the build, and workerd for the local Cloudflare runtime.

allowBuilds:
  esbuild: true
  workerd: true

Vite+ ships its own build of Vite, and every vite in the tree is pointed at it. Bump this alongside the vite-plus devDependency, in every repository at once. Since that build is an npm alias, pnpm can't check it against the usual vite peer ranges, so those checks are off for vite.

overrides:
  "vite@*": "npm:@voidzero-dev/vite-plus-core@1.3.0"

peerDependencyRules:
  allowAny:
    - vite

The versions of the shared tools this repository doesn't use itself. Nothing here installs them, and pnpm leaves a catalog entry alone when nothing uses it. pnpm drift holds every repository that uses one to the version written here, and pnpm align moves them.

catalog:
  publint: ^0.3.25
  typescript: ^7.0.2
  wrangler: ^4.151.0