Skip to content

Repository files navigation

chenv

npmnpmBuild StatusCoverage Status

cli tool to manage Chrome Web Store item.

Why?

  • no need zip
  • credentials in .env is auto loaded
  • capable of manage multiple items

Setup

1. set credentials in .env

CLIENT_ID=XXXXXXXXXX
CLIENT_SECRET=XXXXXXXXXX

2. install and auth

yarn add -D chenv
yarn chenv auth
...
> REFRESH_TOKEN=XXXXXXXXXX

3. set REFRESH_TOKEN in .env

CLIENT_ID=XXXXXXXXXX
CLIENT_SECRET=XXXXXXXXXX
REFRESH_TOKEN=XXXXXXXXXX

Usage

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.

{items: {[name]: {src: string,id: string,}}}

items

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 --all

Ref

License

MIT (http://opensource.org/licenses/MIT)

About

cli for manage Chrome Web Store items

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages