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

In simple NextJS project building on my mac and codesandbox, Getting worry-some warning #15002

Closed
pkellner opened this issue Jul 9, 2020 · 3 comments

Comments

@pkellner
Copy link
Contributor

pkellner commented Jul 9, 2020

Bug report

Getting this warning making me feel like I'm building a time-bomb.

warning next > [email protected]: Chokidar 2 will break on node v14+. Upgrade to
chokidar 3 with 15x less dependencies.
warning next > [email protected]: Legacy versions of mkdirp are no longer supported
. Please update to mkdirp 1.x. (Note that the API surface has changed to use P
romises in 1.x.)
warning next > webpack > watchpack > watchpack-chokidar2 > [email protected]: Cho
kidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependenc
ies.

Describe the bug

The simple project at this codesandbox
https://codesandbox.io/s/bold-elion-qqwdk

generates these warnings:

warning next > [email protected]: Chokidar 2 will break on node v14+. Upgrade to
chokidar 3 with 15x less dependencies.
warning next > [email protected]: Legacy versions of mkdirp are no longer supported
. Please update to mkdirp 1.x. (Note that the API surface has changed to use P
romises in 1.x.)
warning next > webpack > watchpack > watchpack-chokidar2 > [email protected]: Cho
kidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependenc
ies.

To Reproduce

Build with this CodeSandBox
https://codesandbox.io/s/bold-elion-qqwdk

@jamesmosier
Copy link
Contributor

Looks like it is on the radar and upgrading to webpack 5, which is underway, will resolve this.

Issue with other links with more info: #14670 (comment)

@timneutkens
Copy link
Member

Closing as duplicate of #14670

@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 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants