-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[BUG] null not handled by broken npm #6492
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 9.x
work is associated with a specific npm 9 release
Comments
jelmd
added
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 9.x
work is associated with a specific npm 9 release
labels
May 22, 2023
Just in case for reproduction - cleanup the cache, too, e.g. run |
BTW: solved the problem with this patch (not sure, whether this is ok, but at least allowed me going back to back work ;-)): --- /usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js.orig 2023-04-12 05:45:24.000000000 +0200
+++ /usr/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js 2023-05-24 18:15:49.699840640 +0200
@@ -1304,6 +1304,11 @@
continue
}
+ var x = node.parent.edgesOut.get(edge.name);
+ //console.log('\nedge.name=\n', edge.name, '\n', x );
+ if (!x)
+ continue;
+
const parentEdge = node.parent.edgesOut.get(edge.name)
const { isProjectRoot, isWorkspace } = node.parent.sourceReference
const isMine = isProjectRoot || isWorkspace |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 9.x
work is associated with a specific npm 9 release
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
npm is unusable (unable to
npm update
) because of un-handled null properties:Expected Behavior
npm update
should go through w/o any error.Steps To Reproduce
Try this
package.json
:and run
npm i
ornpm update
.Environment
prefer-offline = true
The text was updated successfully, but these errors were encountered: