Package Exports
- putasset
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (putasset) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Putasset

Upload asset to release on github.
Install
npm i putasset -gHow to use?
Global
$ putasset
Usage: putasset [options]
Options:
-h, --help : display this help and exit,
-v, --version : output version information and exit,
-r, --repo : name of repository,
-u, --user : user of repository,
-t, --tag : tag of repository (shoul exist!),
-f, --filename : path to asset
-tn, --token : github token <https://github.com/settings/tokens/new>
$ putasset -tn "token from url" \
-r putasset -o coderaiser -t v1.0.0 \
-f "release.zip"To set token environment variable PUTASSET_TOKEN could be used.
Local
npm i putasset --savePlatforms
For old versions of node.js use:
require('putasset/legacy');For globally installed module: putasset_.
Data will be read before execution in next order (left is more important):
command line -> ~/.putasset.json
Example
const putasset = require('putasset'),
const token = 'token from https://github.com/settings/applications';
putasset(token, {
user: 'coderaiser',
repo: 'putasset',
tag: 'v1.0.0',
filename: 'realease.zip'
}, (error) => {
if (error)
console.error(error.message);
});Related
- grizzly - Create release on github with help of node.
License
MIT