-
Notifications
You must be signed in to change notification settings - Fork 19
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
TypeError when doing npm install because of npm-audit-report #9
Comments
@trickeyone you'll want npm@next I removed Object.entries from later versions of this library which are now included in that version. |
Yeah, can't do that. This is for a production app, so doing next isn't an option. |
@trickeyone understandable. The next release of the cli will likely be this week. |
I just ran into the same issue npm install failed with "npm ERR! Object.entries is not a function" |
It seems that 8814da0 was in v1.0.6-v1.0.8, but was removed before v1.0.9? See npm/npm#20553 as well. |
Given this breaks npm 6.0.0 on node <8, any chance of bringing forward a release of npm with the fix? We have a growing number of users hitting this issue in a PaaS environment where the buildpack (which is outside of our control) is picking up node 6 and npm 6 and we cannot easily change it. |
https://twitter.com/maybekatz/status/994111802827927552 It seems it's fixed in npm "next", which will hopefully be released as "latest" soon. |
@ljharb thanks for the link - good to know it is imminent Appreciate all the work everyone does here. 👍 |
npm v6.0.1 is released (and this repo now contains v1.0.9) so this can be closed. |
I recently upgraded to npm v6 and I'm not getting errors coming from this package. Here is the error from the npm verbose log:
The offending line is
const severities = Object.entries(data.metadata.vulnerabilities).filter((value) => {
OS Info:
Mac OSX Sierra 10.12.6
node: v6.11.4
npm: 6.0.0
The text was updated successfully, but these errors were encountered: