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

automate-chrome-extension-update

v1.0.11

Published

Automate Chrome Extension Update Workflow

Downloads

5

Readme

automate-chrome-extension-update

Automate Chrome Extension Update Workflow

Node 7 is required

More Information on "CLIENT_ID" AND "APP_ID" https://developer.chrome.com/webstore/using_webstore_api

For the first time please create extension.json with following keys

{ "CLIENT_ID": "<CLIENT_ID>", "APP_ID": "<APP_ID>" }

APP_ID

Your extension id, it is generated after the the extension is published to the store. This can be obtained from the url of the extension

CLIENT_ID

  • Go to https://console.developers.google.com/apis/credentials
  • Select Your Project
  • Please make sure Chrome Store API Service is enabled (Library Tab on the left)
  • Create credentials (In Credentials Tab) -> OAuth Client ID -> Application Type: Other
  • There are "CLIENT_ID" and "CLIENT_SECRET"

and run 'node <command.js>'

Preparing commands

updateCode.js

Get the link in the console then open the browser, copy the code and paste into the console

updateToken.js

Automated request the token

Operation commands

These operations require code and token are ready ...

getUploadStatus.js

Simply request the status of the extension

updatePackage.js PATH-TO-ZIP-FILE

The parameter is the absolute path to the zip file to update

Tip

Please see https://github.com/phonglk/chrome-extension-webpack-boilerplate on how to integrate to project