chore: update compatible dependencies#389
Conversation
0a5f9c3 to
b68af49
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b68af498a5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| }, | ||
| "devDependencies": { | ||
| "@opencode-ai/plugin": "^1.3.0" | ||
| "@opencode-ai/plugin": "~1.15.13" |
There was a problem hiding this comment.
Constrain the published plugin peer range
This only pins the workspace dev/test copy of @opencode-ai/plugin; it is not installed for consumers of the published package, while the peer range above still accepts *. In an OpenCode 1.16+ project, or when npm resolves the missing peer during npm install opencode-poe-auth, the package can still be paired with the Node-22-only dependency chain this change is trying to avoid. If 1.16 is incompatible with the supported Node 20 path, the peer range needs the same upper bound or the peer should be made optional/non-resolving.
Useful? React with 👍 / 👎.
Summary
@opencode-ai/pluginon the latest 1.15 patch line foropencode-poe-authto avoid the Node 22+ engine requirement introduced through the 1.16 dependency chain.Validation
npm run buildnpm run lintnpm testnpm audit --omit=optional