npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

chenv

v1.2.3

Published

cli to manage Chrome Web Store item

Downloads

126

Readme

chenv

npm npm Build Status Coverage 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)