Closed fed135 closed 2 years ago
Solve this as people looking for licenses are really sitting in companies with some private repositories.
Perhaps we should add a configuration variable called 'npmTokenEnvVar' (default value: 'NPM_TOKEN') that contains the name of the environment variable with the bearer token for authentication with the private repo (the address of the repository is defined in the configuration variable 'registry' - default value 'https://registry.npmjs.org/').
Would this solve the issue?
If have made a little test that showed that we can always set the authentication header as the public npm repository simply ignores this header. Unfortunately I don't have access to a private npm repository so that I cannot test this feature.
Fixed in next release based on pr #65.
Getting some errors when repo has private packages
The NPM_TOKEN env variable is set and valid