Repository navigation
DEV: Move pnpm settings to pnpm-workspace.yaml - #2
Merged
Merged
Conversation
The skeletons now use pnpm 12, which only reads auth and registry settings from `.npmrc`. The updater now brings over the skeleton's `pnpm-workspace.yaml` and `.npmrc` and merges them into the project's own. - In `pnpm-workspace.yaml`, the skeleton's settings replace the project's, and the project's other settings stay. List settings such as `minimumReleaseAgeExclude` keep the project's entries and add the skeleton's. - `.npmrc` is merged like `.gitignore`: the project keeps its lines and gets the skeleton's settings that it lacks, matched by setting name. `auto-install-peers` and `strict-peer-dependencies` are removed, because pnpm reads them from `pnpm-workspace.yaml`. `engine-strict` stays, because npm reads it and then refuses to install a project whose engines say `"npm": "please-use-pnpm"`. - The install no longer passes `--ignore-workspace`, which would skip `pnpm-workspace.yaml`. The project's own `pnpm-workspace.yaml` keeps the install inside the project. - The test fixtures match the skeletons' TypeScript 7 and pnpm 12 changes. Bumps the package to 0.2.0.
ZogStriP
approved these changes
Oct 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The skeletons now use pnpm 12, which only reads auth and registry settings from
.npmrc. The updater now brings over the skeleton'spnpm-workspace.yamland.npmrcand merges them into the project's own.pnpm-workspace.yaml, the skeleton's settings replace the project's, and the project's other settings stay. List settings such asminimumReleaseAgeExcludekeep the project's entries and add the skeleton's..npmrcis merged like.gitignore: the project keeps its lines and gets the skeleton's settings that it lacks, matched by setting name.auto-install-peersandstrict-peer-dependenciesare removed, because pnpm reads them frompnpm-workspace.yaml.engine-strictstays, because npm reads it and then refuses to install a project whose engines say"npm": "please-use-pnpm".--ignore-workspace, which would skippnpm-workspace.yaml. The project's ownpnpm-workspace.yamlkeeps the install inside the project.Bumps the package to 0.2.0.