docs(angular): document PNPM workaround for ngcc #19041
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix from #18100
Current Behavior
Currently, https://nx.dev/recipes/other/setup-incremental-builds-angular#requirements still warns that
ngcc
doesn't support PNPM.Expected Behavior
While
ngcc
doesn't support PNPM out-of-the-box, PNPM has since added a node-linker=hoisted mode that creates flatnode_modules
without symlinks, similar to thenode_modules
created by NPM, allowingngcc
to work with PNPM (angular/angular#50735).Unfortunately, using
node-link=hoisted
breaks@parcel/watcher
that is used by NX (#16319 and parcel-bundler/watcher#142). A workaround is to explicitly declarenode-gyp-build
inpackage.json
, e.g.This PR documents the workarounds to use
ngcc
with PNPM.p.s. Huge thanks to @DzmVasileusky for discovering the workarounds.