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

Build hangs on "Checking validity of types" with Yarn 3 in PnP mode #34799

Closed
1 task done
srigi opened this issue Feb 25, 2022 · 2 comments
Closed
1 task done

Build hangs on "Checking validity of types" with Yarn 3 in PnP mode #34799

srigi opened this issue Feb 25, 2022 · 2 comments
Labels
bug Issue was opened via the bug report template.

Comments

@srigi
Copy link
Contributor

srigi commented Feb 25, 2022

Verify canary release

  • I verified that the issue exists in Next.js canary release

Provide environment information

/bin/sh: pnpm: command not found

    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 20.6.0: root:xnu-7195.141.19~2/RELEASE_X86_64
    Binaries:
      Node: 16.13.2
      npm: 8.5.2
      Yarn: 3.2.0
      pnpm: N/A
    Relevant packages:
      next: 12.1.1-canary.2
      react: 17.0.2
      react-dom: 17.0.2

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

not deploying, running build locally

Describe the Bug

Creating a default app, switching to Yarn2, and then switching to PnP mode, hangs build process at

Checking validity of types

Terminal hangs on this log infinitely, CPU is not loaded.

Expected Behavior

NPM script should finish the build.

To Reproduce

  • yarn -v (1.22.17)

  • yarn create next-app .

  • yarn set version berry

  • yarn -v (3.2.0)

  • yarn install (migrate yarn.lock to a new format)

  • yarn build
    Build at this point works as usual.

  • change nodeLinker to pnp in .yarnrc.yml

  • yarn install (migrate node_modules to PnP)

  • yarn build
    Hangs...

@srigi srigi added the bug Issue was opened via the bug report template. label Feb 25, 2022
@zigang93
Copy link

Duplicate issue of #34794

@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 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

3 participants