Repository navigation
chore: require Node.js 22 and accept kit 0.3 and schema 0.12 peers - #275
Conversation
Raise engines.node to >=22.0.0 where it was lower. Widen the @wolfstar/kit and @wolfstar/schema peer ranges to also accept the 0.3 and 0.12 lines.
|
Note The title starts with
|
wolfstarbot
added
packages:plugin-api
![pullfrog[bot]](https://avatars.githubusercontent.com/in/1768019?s=60&v=4){kind=small}
There was a problem hiding this comment.
ℹ️ No critical issues — two small inconsistencies worth fixing before merge.
Reviewed changes
Reviewed the single commit: the Node floor and the kit/schema peer ranges across the ten packages, plus the changesets, AGENTS.md and the module-entries test.
- Node 22 floor:
engines.nodebecomes>=22.0.0in the eight packages that were on>=20. The changeset bumps (major forplugin-api,plugin-i18nextandplugin-subcommands-advanced, minor for the 0.x packages) match their current versions. - Peer ranges:
@wolfstar/kitis^0.2.0 || ^0.3.0and@wolfstar/schemais^0.9.0 || ^0.12.0in all ten packages. These are the correct caret semantics for 0.x versions, and the dev ranges are left alone. - Docs and test:
AGENTS.mdandtests/module-entries.test.tsfollow the new ranges.
ℹ️ plugin-api README still advertises Node >=20.18.1
packages/plugin-api/README.md:30 ("Requires Node.js >=20.18.1.") and :257 (the peer-range note ending in "Node.js >=20.18.1") now contradict engines.node. They are outside the diff, so I can't anchor them inline. The old design docs under docs/superpowers/ also mention >=20, but those are historical and can stay.
claude-sonnet-5-5 ｜ 𝕏
…gin-api README plugin-i18next depends on chokidar 6, which needs Node 22.22. The plugin-api README still named Node 20.18.1 and omitted framework 6.
@wolfstar/plugin-api
@wolfstar/plugin-broker
@wolfstar/plugin-cache
@wolfstar/plugin-gateway
@wolfstar/plugin-i18next
@wolfstar/plugin-logger
@wolfstar/plugin-opentelemetry
@wolfstar/plugin-scheduled-tasks
@wolfstar/plugin-sharder
@wolfstar/plugin-subcommands-advanced
commit: |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Reviewed the new commit 28e3651 since the prior Pullfrog review of abacabd.
plugin-i18nextengines: raisedengines.nodeto>=22.22.0to matchchokidar6, andAGENTS.mdnow lists it next to the other higher floors.plugin-apiREADME: the install note now says Node>=22.0.0, and the peer-range note lists^3.6.0 || ^5.0.0 || ^6.0.0with Node>=22.0.0, matchingpackage.json.
claude-sonnet-5-5 ｜ 𝕏
🔗 Linked issue
None. Related to #272, which bumps
@wolfstar/kitto 0.3 and@wolfstar/schemato 0.12 as dev dependencies.🧭 Context
Node.js 20 is end of life, and the published packages still declare
>=20. Separately,@wolfstar/kit0.3 and@wolfstar/schema0.12 fall outside the^0.2.0and^0.9.0peer ranges, so a project on the new versions gets peer warnings from every plugin. Once #272 merges,pnpm peers checkin this workspace reports the same warnings.📚 Description
Raises the minimum Node.js version to 22 and widens the kit and schema peer ranges so both the old and the new versions are accepted.
Key changes
engines.nodeis>=22.0.0in the eight packages that were on>=20, exceptplugin-i18nextat>=22.22.0becausechokidar6 needs it.plugin-gateway(>=24.17.0) andplugin-opentelemetry(>=22.15.0) already required more.@wolfstar/kitpeer range:^0.2.0becomes^0.2.0 || ^0.3.0.@wolfstar/schemapeer range:^0.9.0becomes^0.9.0 || ^0.12.0.tests/module-entries.test.ts,AGENTS.mdand theplugin-apiREADME follow the new ranges.plugin-api,plugin-i18next,plugin-subcommands-advanced) and a minor for the 0.x ones. The peer ranges are a patch for every package.Type of Change
Pre-flight Checklist
pnpm changeset(orpnpm changeset add --emptyif no release is needed). See .changeset/README.md.