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

@auto-it/chrome

v11.2.1

Published

Chrome publishing plugin for auto

Downloads

3,017

Readme

Chrome Web Store

This plugin allows you to automate the publishing of chrome extensions

Example Repo: here

Prerequisites

To publish to the chrome web store you will need the following secrets set in your environment. See here for a guide one how to get these values.

  • CLIENT_ID
  • CLIENT_SECRET
  • REFRESH_TOKEN

Installation

This plugin is not included with the auto CLI installed via NPM. To install:

npm i --save-dev @auto-it/chrome
# or
yarn add -D @auto-it/chrome

WARNING: You can only use one "package manager" at a time! Mixing them will lead to undesired results.

Usage

You must first pack/zip your plugin before running auto.

These environment variables tell auto what to publish.

  • EXTENSION_ID - your chrome extensions unique ID (REQUIRED)
  • EXTENSION_BUILD - Path to either a zip file, or a directory to be zip. defaults to extension.zip

Or you can set these values in the autorc:

{
  "plugins": [
    [
      "chrome",
      {
        "id": "1234",
        "build": "path/to/zip/or/folder",
        "manifest": "path/tp/manifest.json"
      }
    ]
  ]
}

:warning: You must have a manifest.json for this plugin to work.