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

Missing webpack as peerDependency #30481

Closed
rtritto opened this issue Oct 27, 2021 · 2 comments
Closed

Missing webpack as peerDependency #30481

rtritto opened this issue Oct 27, 2021 · 2 comments
Labels
bug Issue was opened via the bug report template.

Comments

@rtritto
Copy link

rtritto commented Oct 27, 2021

What version of Next.js are you using?

12.0.1

What version of Node.js are you using?

14.17.0

What browser are you using?

Chrome

What operating system are you using?

Windows

How are you deploying your application?

Vercel

Describe the Bug

react-server-dom-webpack dependency have webpack as peerDependency and it should be added in peerDependency of next.

Expected Behavior

No warnings in yarn log.

To Reproduce

  1. yarn init -y
  2. yarn set version berry (latest stable version of yarn berry is 3.1.0)
  3. yarn add next react react-dom

Output:

...
➤ YN0002: │ next@npm:12.0.1 [02103] doesn't provide webpack (pfa00f), requested by react-server-dom-webpack
...

Additional:

$ yarn explain peer-requirements pfa00f
➤ YN0000: next@npm:12.0.1 [02103] doesn't provide webpack, breaking the following requirements:

➤ YN0000: react-server-dom-webpack@npm:0.0.0-experimental-3c4c1c470-20211021 [f848f] → ^4.43.0 ✘
@rtritto
Copy link
Author

rtritto commented Oct 28, 2021

Fixed on #30505

@rtritto rtritto closed this as completed Oct 28, 2021
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

2 participants