yarn pnp with `ng add angular-eslint` fails on v20

[JamesHenry]

Command

add

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Discovered when proving that yarn pnp is no longer an issue on the angular-eslint side: angular-eslint/angular-eslint#1091 (comment)

Minimal Reproduction

yarn dlx @angular/cli new --package-manager yarn
yarn install # to confirm no issues yet
yarn ng add angular-eslint@20.0.0-alpha.1 # blows up per the below screenshot

---

This worked though:

• add angular-eslint@20.0.0-alpha.1 manually to package.json and run yarn install (no yarn pnp install errors, I think proving it's not an angular-eslint package issue)
• run ng add angular-eslint as normal and it now succeeds

Exception or Error

Your Environment

Angular CLI: 20.0.0
Node: 22.16.0
Package Manager: yarn 4.9.1-git.20250411.hash-1908ee79f
OS: darwin arm64

Angular: 20.0.0
... build, cli, common, compiler, compiler-cli, core, forms
... platform-browser, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.2000.0 (cli-only)
@angular-devkit/core         20.0.0 (cli-only)
@angular-devkit/schematics   20.0.0 (cli-only)
@schematics/angular          20.0.0 (cli-only)
rxjs                         7.8.2
typescript                   5.8.3
zone.js                      0.15.1

Anything else relevant?

No response

[alan-agius4]

This seems a to be caused by @listr2/prompt-adapter-inquirer which has listr2 listed as a devDependency instead of a dependency.

Closing as this is not actionable from our end.

[JamesHenry]

Whilst technically true, you are ultimately choosing to use that dependency and the experience being described is relevant for any of your users that run ng add 🤔 why close this without further reporting onto the relevant dependency (or move away from them)? Surely it's just going to be reported again by someone else?

[alan-agius4]

I have opened a PR to fix it listr2/listr2#740

[JamesHenry]

Ah, even better! Thanks a lot 🙏