docs: add Node.js 22 requirement across skills#72
Open
pyramation wants to merge 1 commit intomainfrom
Open
Conversation
- constructive-setup: add Prerequisites section with Node.js 22+ and pnpm 10+ requirements, add 'Verify Node.js Version' as step 1 - constructive-testing: add 'Use Node.js 22+' as critical rule #1 - pgpm/ci-cd: update workflow template from node-version 20 to 22, add best practices for Node.js 22 and --frozen-lockfile - pnpm-workspace: update compatibility from Node.js 18+ to Node.js 22+ Node.js 20 causes different pnpm module resolution behavior that leads to duplicate graphql module instances and 'Cannot use GraphQLObjectType from another module or realm' runtime errors with PostGraphile/Graphile packages.
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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
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.
Summary
Adds Node.js 22 as a documented requirement across four skill files. This was discovered while debugging
pyramation-studio/agentic-dbCI failures where Node.js 20 caused pnpm to resolve duplicategraphqlmodule instances (16.13.0 and 16.13.1), producing "Cannot use GraphQLObjectType from another module or realm" runtime errors with PostGraphile/Graphile packages.Files changed:
constructive-setup/SKILL.md— New "Prerequisites" section with Node.js 22+ and pnpm 10+ requirements; new "Verify Node.js Version" as step 1 (renumbers subsequent steps)constructive-testing/SKILL.md— "Use Node.js 22+" added as Critical Rule skills for codegen #1pgpm/references/ci-cd.md— Workflow template updated fromnode-version: '20'→'22'; two new best practices added (Node.js 22 and--frozen-lockfile)constructive-tooling/references/pnpm-workspace.md— Compatibility updated fromNode.js 18+toNode.js 22+Note:
pgpm/SKILL.mdalready hadNode.js 22+in its compatibility field — this PR aligns the rest of the skills to match.Review & Testing Checklist for Human
pnpm.overrides, etc.).Notes
--frozen-lockfilebest practice was added toci-cd.mdas it was also instrumental in fixing the CI issue (prevents silent dependency drift between local and CI).node-version: '20'— agents copying this template would reproduce the exact issue we debugged.Link to Devin session: https://app.devin.ai/sessions/342b041cb9ff4dcbaaba21b3141f69c5
Requested by: @pyramation