docs: fold pnpm into the ecosystem caveat#866
Merged
Conversation
Extend the existing reusable-CI/org-secrets note so it also states that modules from this template use pnpm internally, and point npm-preferring authors to swap the pnpm commands when working outside the organization.
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
1 participant
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.
Extends the existing reusable-CI/org-secrets note in the README so it also states that modules created from this template use pnpm internally (via the
packageManagerfield andpnpm-workspace.yaml), and points npm-preferring authors working outside the gethinode organization to swap the pnpm commands for their npm equivalents.README-only; one line changed. Completes the module-development caveat pass alongside the gethinode.com docs.