fix(arborist): add missing top property to isolated reifier proxy nodes#9064
Conversation
|
This is exactly the kind of thing we knew to expect with all of the pseudo node/link/etc objects that the isolated reifier was making. Thanks for picking this up. Is there a reason this is a PR to v10? Usually we land things in |
Explained in the linked issue
|
|
Would it be preferable to pull in that npm 11 change instead? |
I did think about it first but the npm 11 change (f6c868d) touches 5 files (reify.js, diff.js, node.js, snapshot, tests) and restructures how omit is calculated — moving it from This PR is a minimal fix (3 lines + test) scoped to the crash only. Happy to go either way — I can attempt the backport if you'd prefer that approach, or we can land this as a targeted fix for v10. Separately, I have a fix for a related issue on |
This is what we really want here. That's good enough for us! Thanks. |
In continuation of our exploration of using
install-strategy=linkedin the Gutenberg monorepo, which powers the WordPress Block Editor.##Summary
Fixes
npm install --omit=devcrashing withinstall-strategy=linkedin workspace monorepos.addOmitsToTrashListiterates inventory nodes and accessesnode.top.isProjectRoot, but the isolated reifier's proxy nodes for the root, workspace, and workspace link were missing thetopproperty, causing aTypeError.top(self-reference) to root and workspace proxy nodestop: rootto workspace link proxy nodesisWorkspace: trueto workspace proxy nodes so their dev deps can be omittedReferences
Fixes #9063