Package Exports
- chenv
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 (chenv) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
chenv
cli tool to manage Chrome Web Store item.
Why?
- no need zip
- credentials in
.envis auto loaded - capable of manage multiple items
Setup
1. set credentials in .env
CLIENT_ID=XXXXXXXXXX
CLIENT_SECRET=XXXXXXXXXX2. install and auth
yarn add -D chenv
yarn chenv auth
...
> REFRESH_TOKEN=XXXXXXXXXX3. set REFRESH_TOKEN in .env
CLIENT_ID=XXXXXXXXXX
CLIENT_SECRET=XXXXXXXXXX
REFRESH_TOKEN=XXXXXXXXXXUsage
Usage: chenv [options] [command]
Options:
-V, --version output the version number
-h, --help output usage information
Commands:
auth [options] get REFRESH_TOKEN easily
upload [options] [src] [id] upload item (!id ? insert : update)
remove [options] [id] not remove but update item as "removed-like"WARNING: No way to remove item from dashboard, Don't forget to set id when update item by upload. Or new item that has same name will be created.
Config
chenv has a tiny config. In default chenv.config.js or "chenv" in package.json that sits in the process.cwd() is used.
{
alias: {
[name]: {
src: string,
id: string,
}
}
}alias
Used for mapped by -a, --alias-name and --all option.
Not sure but may be helpful in the case that manages multi items clearly.
chenv upload -a item1,item2
chenv upload --allRef
- Using the Chrome Web Store Publish API
- Chrome Web Store Developer Dashboard - Delete Extensions
- Remove app from Developer Dashboard