3
0
Fork 0
mirror of https://gitea.com/actions/setup-node.git synced 2024-11-25 11:39:32 +01:00
setup-node/node_modules/btoa-lite/README.md
Danny McCormick 78148dae50
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
2019-08-06 18:26:04 -04:00

1.2 KiB

btoa-lite

Smallest/simplest possible means of using btoa with both Node and browserify.

In the browser, encoding base64 strings is done using:

var encoded = btoa(decoded)

However in Node, it's done like so:

var encoded = new Buffer(decoded).toString('base64')

You can easily check if Buffer exists and switch between the approaches accordingly, but using Buffer anywhere in your browser source will pull in browserify's Buffer shim which is pretty hefty. This package uses the main and browser fields in its package.json to perform this check at build time and avoid pulling Buffer in unnecessarily.

Usage

NPM

encoded = btoa(decoded)

Returns the base64-encoded value of a string.

License

MIT. See LICENSE.md for details.