Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unmet peer dependency: @types/node #1584

Closed
mark-dr opened this issue Oct 25, 2024 · 0 comments · Fixed by #1585
Closed

Unmet peer dependency: @types/node #1584

mark-dr opened this issue Oct 25, 2024 · 0 comments · Fixed by #1585

Comments

@mark-dr
Copy link

mark-dr commented Oct 25, 2024

PR #1569 caused some unmet peer dependency errors. In my package that uses @inquirer/confirm@5.0.0 (via msw), Yarn 3.6.1 emits:

➤ YN0002: │ @inquirer/confirm@npm:5.0.0 doesn't provide @types/node (...),  requested by @inquirer/type
➤ YN0002: │ @inquirer/core@npm:10.0.0 doesn't provide @types/node (...), requested by @inquirer/type

The rule Yarn applies is that all packages should either satisfy the peer dependencies of their dependencies, or redeclare them in their own peer dependencies. Looks like this could be solved by adding @types/node to the peer dependencies of @inquirer/core and @inquirer/confirm.

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 a pull request may close this issue.

1 participant