Unable to authenticate on registries

[WarningImHack3r]

What is the issue?

Since 3.6.0, I've removed the fallbacks using terminal commands to remove the dependency on shell command execution, as it's slow and now (I thought) useless (#104).

However, as private repositories are indeed still fetchable and scanned, I no longer enjoy the benefit that running npm commands from a shell gives me authenticated access for free thanks to the npm command doing all the work for me.

I could easily revert the changes I made, but I don't want to for performance reasons and issues like #104.

I need to read credentials in a way (reading the global config?) such that I can use them to authenticate my requests without having to run npm commands again.

Note

If you read this because you're affected by the issue and had no problem with command executions before, you can temporarily downgrade to 3.5.0 while waiting for a better fix.

What are the steps to reproduce this issue?

Have a private authenticated registry and/or a private package, run the plugin.

What were you expecting to happen?

The plugin to work as well as it did before 3.6.0.

Paste any relevant logs, error output, etc.

No response

What OS are you experiencing the problem on?

Not applicable

Additional platform information

No response

Duplicates

• I have checked that my problem has not already been mentioned recently in an existing issue