Skip to content

Version constraints too tight for npm i to resolve #367

@ochafik

Description

@ochafik

In this PR's CI, npm i never completes: modelcontextprotocol/example-remote-server#35
(bun i seems to have a better constraints solver and runs relatively quickly)

The version pinning used in package.json for quite a few packages looks way too aggressive and needs relaxing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions