michael faith

Is there any movement on this, by chance? I've had some teams asking for this recently, and the possible workarounds don't really work very well. Doesn't seem to be a...

I'm excited to have this as an option now!

Progress! I'm excited that it's closer to being resolved. @dgerhardt I wonder if it might not be better to open a new issue in the angular/components repo for this, since...

@dgerhardt excellent! Thanks for the info.

@johncrim thanks for the investigation and for opening the issues to resolve. It's something I'm eager to take advantage of.

> For what it's worth; we've added an e2e test in the Yarn repo verifying that the Angular CLI and PnP work [yarnpkg/berry#3949](https://github.com/yarnpkg/berry/pull/3949) This is exciting news

Curious about that as well.

> ``` > Error: Failed to initialize Angular compilation - Cannot locate the 'node_modules' directory. > > ✖ Failed to compile. > ``` Searching for that error in the repo,...

> That's the case for yarn only, npm should still report an error Why should it report an error in this logic? This logic is only responsible for running the...

> This package resolution does not yet support custom conditions for the package `exports` field. So for other packages that use the `exports` field this may not work yet. So...