Skip to content

docs(readme): npm peer-dependency (ERESOLVE) upgrade guidance (#187)#193

Merged
stackbilt-admin merged 1 commit into
mainfrom
docs/187-npm-peer-deps-guidance
May 30, 2026
Merged

docs(readme): npm peer-dependency (ERESOLVE) upgrade guidance (#187)#193
stackbilt-admin merged 1 commit into
mainfrom
docs/187-npm-peer-deps-guidance

Conversation

@stackbilt-admin
Copy link
Copy Markdown
Member

Closes #187.

Installing/upgrading @stackbilt/cli can trip npm's strict peer resolver when the consumer's tree already has a conflicting peer range (e.g. a package peering zod@^4 against Charter's zod@^3). The conflict is consumer-side — Charter's CLI has no agents dep and its runtime is unaffected once installed.

Adds a README Install subsection documenting both fixes (--legacy-peer-deps for a fast unblock, or aligning the conflicting dep at its source) and noting pnpm/yarn resolve without the flag.

Docs only.

🤖 Generated with Claude Code

Installing/upgrading @stackbilt/cli can trip npm's strict peer resolver
when the consumer's tree already has a conflicting peer range (e.g. a
package peering zod@^4 against Charter's zod@^3). The conflict is
consumer-side and Charter's runtime is unaffected once installed.

Document both fixes — --legacy-peer-deps for a fast unblock, or aligning
the conflicting dependency at its source — and note pnpm/yarn resolve
without the flag.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@stackbilt-admin stackbilt-admin merged commit b497b32 into main May 30, 2026
5 checks passed
@stackbilt-admin stackbilt-admin deleted the docs/187-npm-peer-deps-guidance branch May 30, 2026 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(cli): npm upgrade to @stackbilt/cli@1.0.0 can require --legacy-peer-deps

1 participant