Cannot convert undefined or null to object Exiting about audit-ci

[aarbro]

We were having the same issue after upgrading to node 16 and audit-ci 6.2.x.

I just figured out that we had a private registry in the project's .npmrc file. Once I overrode the registry to the default via the audit-ci command line (e.g. audit-ci --registry https://registry.npmjs.org), I no longer got the error. Setting it in the audit-ci config file worked also.

You can reproduce the error by simply specifying a bogus registry (e.g. audit-ci --registry http://localhost).

@quinnturner It would be great to get a fix for this, as it has caused lots of confusion!

[quinnturner]

Do you have a lockfile?

Also, please consider updating to the latest audit-ci, especially since you're using NPM v8. It's pretty much a rewrite of the dependency management algorithm and is pretty much required nowadays.

[agnosticcloud]

Yes we have a lockfile, and we are also running into this error when using the latest version of audit-ci.

[quinnturner]

Do you have private dependencies?

Is it possible for you to email me the package.json and lockfile? You can remove the name of the project; I'd like a reproduction to help understand where the issue occurs. quinnDOTturnerATuwaterlooDOTca

[1sherlynn]

Are there any updates/findings on this? Also facing a similar issue.
When using node v12 and npm v6.14.15, this issue is not present.

Issue:

audit-ci version: 6.0.0
Cannot convert undefined or null to object
Exiting...

Versions used which is associated with the issue:

Audit-ci: 6.2.0 (latest at the moment)
NPM: 8.1.2
Nodejs: v16.13.2

[quinnturner]

Thank you @1sherlynn for the report! Good to know that it's still occurring and that it's on NPM 8. Hoping you can post the result of this command: npm audit --json

[quinnturner]

Thanks for the heads up @aarbro, will look into it and mark this as a bug!

[quinnturner]

PR to resolve the registry issue @aarbro mentioned (and might catch other NPM 7+ related issues): #258

[quinnturner]

Released in 6.2.1. If you're still having this issue, please message!