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

Investigate issue with @next version and peerDependencies #494

Closed
1 of 2 tasks
timotheeguerin opened this issue Apr 29, 2022 · 3 comments · Fixed by #544
Closed
1 of 2 tasks

Investigate issue with @next version and peerDependencies #494

timotheeguerin opened this issue Apr 29, 2022 · 3 comments · Fixed by #544
Assignees
Milestone

Comments

@timotheeguerin
Copy link
Member

timotheeguerin commented Apr 29, 2022

If you replace the version in your package.json with "next" seems to be 2 issues:

  • npm install doesn't actually install them -> need npm update
  • It doesn't install the peerDependencies forcing all of them to be expliciltiy specified in the package.json
@ghost ghost added the Needs Triage label Apr 29, 2022
@timotheeguerin
Copy link
Member Author

The issue with peerDependency was that the package wasn't specifying the peerDependency and this is something that was added in the current dev version so it seems like using dev version was causing issue

@timotheeguerin
Copy link
Member Author

For part 1 this seems to be a by design issue with npm npm/cli#3755

@timotheeguerin
Copy link
Member Author

I guess we can document you need to run npm update when switching to the preview build

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.

2 participants