ado-npm-auth 0.1.1 → 0.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +0 -8
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -12,14 +12,6 @@ You can run the binary `"ado-npm-auth"` via `yarn ado-npm-auth` or `npm exec ado
|
|
|
12
12
|
|
|
13
13
|
It will then shell out to the `azureauth` package on [npm](https://www.npmjs.com/package/azureauth), retrieve a token, and update your `~/.npmrc`.
|
|
14
14
|
|
|
15
|
-
## Beware the chicken and egg problem
|
|
16
|
-
|
|
17
|
-
You may need to set the registry to the public NPM feed when running `npm exec` or `npx`.
|
|
18
|
-
|
|
19
|
-
If that's the case, set the environment variable `npm_config_registry=https://registry.npmjs.org`.
|
|
20
|
-
|
|
21
|
-
That will ensure that `npx` or `npm exec` grabs from the public NPM feed, bypassing the soon-to-be authenticated ADO feed.
|
|
22
|
-
|
|
23
15
|
## ado-npm-auth vs vsts-npm-auth
|
|
24
16
|
|
|
25
17
|
The main difference between the two is how they function, and where they can run. The `vsts-npm-auth` tool is Windows only, and uses MSAL authentication.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "ado-npm-auth",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.2",
|
|
4
4
|
"description": "The ado-npm-auth package can automatically use the azureauth CLI to fetch tokens and update a user's .npmrc file for authenticating to ADO package feeds.",
|
|
5
5
|
"repository": "https://github.com/microsoft/ado-npm-auth",
|
|
6
6
|
"license": "MIT",
|