Skip to content

[Bug] Declaring the dependency valibot with a caret #224

@Chloe-He

Description

@Chloe-He

Describe the bug

Is there any chance we can declare the dependency valibot with a caret(^). Because we met a peer dependency issue when trying to install storybook mcp and we pin the version of valibot

.
└─┬ @storybook/addon-mcp 0.3.4
  └─┬ @tmcp/adapter-valibot 0.1.5
    └─┬ @valibot/to-json-schema 1.6.0
      └── ✕ unmet peer valibot@^1.3.0: found 1.2.0 in @storybook/addon-mcp

Steps to reproduce the behavior

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots and/or logs

If applicable, add screenshots and/or logs to help explain your problem.

Environment

  • OS: [e.g. iOS]
  • Node.js version: [e.g. v12.17.0]
  • NPM version: [e.g. 6.14.4]
  • Browser (if applicable): [e.g. chrome, safari]
  • Browser version (if applicable): [e.g. 22]
  • Device (if applicable): [e.g. iPhone6]

Additional context

Add any other context about the problem here.

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