You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TLDR: I am trying to install two versions of a vulnerable package, both are needed. Getting Cannot read properties of null (reading 'name') and packages are not installed.
Expected Behavior
Two versions could be installed together. I also added vulnerabilities to allowlist of audit-ci, but still can 't install.
Steps To Reproduce
Using Windows 11, with the latest nodejs and npm version.
I have no other file, to be able to test properly.
C:\scripts\test> npm i
npm error Cannot read properties of null (reading 'name')
npm error A complete log of this run can be found in: C:\Users\sahin\AppData\Local\npm-cache\_logs\2024-11-19T19_31_49_077Z-debug-0.log
This package does not have a dependency, so it is not related to dependencies. Also adding audit-ci and allowing these vulnerabilities also does not change this behaviour
Environment
npm: 10.9.0
Node.js: 22.11.0
OS Name:
System Model Name: Windows 11
npm config:
PS C:\scripts\test> npm config ls
; node bin location = C:\Program Files\nodejs\node.exe; node version = v22.11.0; npm local prefix = C:\scripts\test; npm version = 10.9.0; cwd = C:\scripts\test; HOME = C:\Users\skasap; Run `npm config ls -l` to show all defaults.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
TLDR: I am trying to install two versions of a vulnerable package, both are needed. Getting
Cannot read properties of null (reading 'name')
and packages are not installed.Expected Behavior
Two versions could be installed together. I also added vulnerabilities to allowlist of audit-ci, but still can 't install.
Steps To Reproduce
I have no other file, to be able to test properly.
It generates
Cannot read properties of null (reading 'name')
or
these work properly.
Also, same problem does not happen with at least one safe package, for example:
This package does not have a dependency, so it is not related to dependencies. Also adding audit-ci and allowing these vulnerabilities also does not change this behaviour
Environment
The text was updated successfully, but these errors were encountered: