You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes the peer-dependency conflict a fresh npm install pgpm@5.30.5 reports:
npm warn Conflicting peer dependency: postgraphile@5.0.3
npm warn peer postgraphile@"5.0.3" from graphile-search@1.21.6
npm warn peerOptional graphile-search@"^1.18.0" from graphile-llm@1.15.8
Root cause: graphile-llm still declared peerDependencies["graphile-search"] = "^1.18.0" while the workspace (and graphile-settings) ship graphile-search@2.14.6. npm satisfies the stale optional peer by hoisting the last 1.x (1.21.6, which pins exact peers postgraphile@5.0.3, graphile-build@5.0.2, …) next to the 2.14.6 the rest of the tree uses — an extraneous second copy with peers a minor behind. graphile-llm is already built and tested against the workspace 2.x via its devDependencies, so the pin was simply never bumped.
Only stale internal peer in the repo (checked every peerDependencies entry naming a workspace package against that package's current version).
Also: constructive-monorepo-setup skill said "Node.js 20+"; the root engines and postgraphile/grafast/@dataplan/pg all declare node >=22 (and grafast needs Promise.withResolvers), so the skill now says 22+. Companion doc fixes: constructive.io prerequisites page and constructive-platform README.
This PR makes two small, coherent changes: it raises the graphile-search peerDependency from ^1.18.0 to ^2.0.0 in graphile/graphile-llm/package.json, and it updates the constructive-monorepo-setup skill to require Node.js 22+ instead of 20+. The peer bump aligns with the already-published graphile-search 2.x line and the imports in the package's tests, and the Node floor is a documentation-only change with no code impact. No contradictory constraints or version disagreements were found.
Files
Change
graphile/graphile-llm/package.json
Raises the graphile-search peerDependency to ^2.0.0, aligning the manifest with the 2.x API the package already uses.
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
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
Fixes the peer-dependency conflict a fresh
npm install pgpm@5.30.5reports:Root cause:
graphile-llmstill declaredpeerDependencies["graphile-search"] = "^1.18.0"while the workspace (andgraphile-settings) shipgraphile-search@2.14.6. npm satisfies the stale optional peer by hoisting the last 1.x (1.21.6, which pins exact peerspostgraphile@5.0.3,graphile-build@5.0.2, …) next to the 2.14.6 the rest of the tree uses — an extraneous second copy with peers a minor behind.graphile-llmis already built and tested against the workspace 2.x via itsdevDependencies, so the pin was simply never bumped.Only stale internal peer in the repo (checked every
peerDependenciesentry naming a workspace package against that package's current version).Also:
constructive-monorepo-setupskill said "Node.js 20+"; the rootenginesand postgraphile/grafast/@dataplan/pg all declarenode >=22(and grafast needsPromise.withResolvers), so the skill now says 22+. Companion doc fixes: constructive.io prerequisites page and constructive-platform README.Link to Devin session: https://app.devin.ai/sessions/6d533da4fa5a48399ad2c7508dffa32b
Open in Devin Desktop: https://app.devin.ai/desktop/session/6d533da4fa5a48399ad2c7508dffa32b?variant=devin
Requested by: @pyramation