Yarn 2 Dependency Issues

Bug report

Describe the bug

There seems to be some dependency issues with v9.3.4 when using Yarn 2. First one I ran into seems to be here: https://github.com/zeit/next.js/blob/7f8f149f9986afd8cb916e27eb231bacaad9dc9d/packages/next/build/utils.ts#L6 I was able to work around it by unplugging next, and changing that to next/dist/compiled/strip-ansi.

But then I started hitting other roadblocks. For example, autodll-webpack-plugin is using find-cache-dir (which I noticed is listed as an external), but it is not listed as a dependency for that package. As a matter of fact, its package.json appears to be quite minimal. It looks to me to be a product of the your build process? I’ll be honest: I didn’t take much time to analyze it. I thought you guys would be better equipped to deal with this.

To Reproduce

• Clone my reproduction repository

• Run yarn

• Run yarn dev

Expected behavior

It should start the dev server

System information

• OS: Linux
• Browser (if applies): Chrome
• Version of Next.js: v9.3.4

Additional context

v9.3.3 works fine 🤷‍♂️

[timneutkens]

This has been fixed already today:

• The strip-ansi case was removed (see #11684)
• mkdir was missing (see #11699)
• find-cache-dir was missing (see #11699)

[balazsorban44]

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.