Add auth support (#21)

* Updates

* Update

* Update

* Update

* Update

* Yarn sometimes prefers npmrc, so use same token

* Description

* Update readme

* Feedback

* Add type

* new toolkit and scoped registries

* npmrc in RUNNER_TEMP

* Dont always auth

* Try exporting blank token

* Get auth working for now pending runner changes

* Fix string interpolation for auth token.

* Don't export both userconfigs

* Update authutil.js

* Add single quotes for authString

* Fix the registry string.

* Use userconfig and append trailing slash

* Keep in root of repo

* Try just adding auth token

* Remove auth token

* Try changes again

* Add tests

* Npm and GPR samples

* Add types
This commit is contained in:
Danny McCormick 2019-08-06 18:26:04 -04:00 committed by GitHub
parent 0675b87d74
commit 78148dae50
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
391 changed files with 79848 additions and 43 deletions

30
node_modules/windows-release/index.d.ts generated vendored Normal file
View file

@ -0,0 +1,30 @@
/**
Get the name of a Windows version from the release number: `5.1.2600` `XP`.
@param release - By default, the current OS is used, but you can supply a custom release number, which is the output of [`os.release()`](https://nodejs.org/api/os.html#os_os_release).
Note: Most Windows Server versions cannot be detected based on the release number alone. There is runtime detection in place to work around this, but it will only be used if no argument is supplied, or the supplied argument matches `os.release()`.
@example
```
import * as os from 'os';
import windowsRelease = require('windows-release');
// On a Windows XP system
windowsRelease();
//=> 'XP'
os.release();
//=> '5.1.2600'
windowsRelease(os.release());
//=> 'XP'
windowsRelease('4.9.3000');
//=> 'ME'
```
*/
declare function windowsRelease(release?: string): string;
export = windowsRelease;