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

node-chrome-webstore

v1.0.8

Published

Update and publish chrome extension automatically.

Downloads

3

Readme

node chrome webstore

Update and publish chrome extension automatically.

Prepare

If you have refresh_token, you can visit Subsequent calls directly.

Else please follow Using the Chrome Web Store Publish API instructions and come back when you get client id, client secret and code.

Code can only be used once, mainly use refresh token later.

Installation

npm i node-chrome-webstore

Usage

First call

Save refresh token and use it in subsequent calls

const webstore = require('node-chrome-webstore');

const client_id = '';
const client_secret = '';
const code = '';

webstore.auth({
  client_id,
  client_secret,
  code,
});

webstore.items.getRefreshToken().then((token) => {
  console.log(token); // save it
});

Subsequent calls

const webstore = require('node-chrome-webstore');

const client_id = '';
const client_secret = '';
const refresh_token = '';
const itemId = '';
const zipPath = '';

webstore.auth({
  client_id,
  client_secret,
  refresh_token,
});

// update
webstore.items.update(itemId, zipPath).then(res => {
    console.log(res);
});

// publish
webstore.items.publish(itemId).then(res => {
    console.log(res);
});

With dotenv example

dotenv can help to save auth info to .env in project root.

Strongly recommend against committing your .env file to version control. It should be in .gitignore.

.env

client_id=9867219971
client_secret=5d21TdajfIcK
refresh_token=1/jBtQRAjjy
code=4/lgAZRFXy
itemId=eppeghhopeo
zipPath=path/to/zip

Read auth info from .env

const webstore = require('node-chrome-webstore');

require('dotenv').config();

const {
  client_id,
  client_secret,
  refresh_token,
  itemId,
  zipPath,
} = process.env;

webstore.auth({
  client_id,
  client_secret,
  refresh_token,
});

webstore.items.update(itemId, zipPath).then((res) => {
  if (res.uploadState === 'SUCCESS') {
    webstore.items.publish(itemId).then((res) => {
      console.log(res);
    });
  } else {
    console.log(res);
  }
});

Development

Test

npm test