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

crxify

v1.0.0

Published

Command line utility for building chrome crx files

Downloads

8

Readme

crxify

Command line utility for building chrome crx files

Inspired by browserify (and more specifically, by watchify) - this tool was created in order to automate the process of packing a Chrome app or extension.

It watches the extension's directory and packs it to a crx file every time there's a change. (For one time, non-watched such builds, please see the excellent crx module).

Installation

npm install crxify

Usage

  Usage: crxify [options]

  Options:

    -h, --help                 output usage information
    -V, --version              output the version number
    -e, --extension-lib [lib]  Extension library to watch, defaults to ./public
    -o, --out-file [file]      crx output file path, defaults to ./extension.crx
    -p, --private-key [key]    Private key to pack the crx (required)

Crxify intentionally does not create a private key file for you. In order to create one, please see: https://help.github.com/articles/generating-ssh-keys/ (among others)

Example Use Cases

Given the following library structure:

├── lib
├── LICENSE
├── package.json
├── extension.crx
├── public
└── README.md

Development is done in ./lib and then watchified/browserified to ./public.

Once it reaches ./public, it is crxified into extension.crx and can then immediately be loaded into Chrome.

This can be achieved by (assuming we're just doing some transpiling):

// package.json
{ 
  ...
  "scripts": {
    "watch-app": "watchify lib/app.js -t babelify --outfile public/js/bundle.js -v",
    "watch": "crxify -p /path/to/my/privateKey.pem & npm run watch-app"
  }
}

Then by simply executing:

npm run watch

Contributions / Issues

Please feel free to open an issue or a PR if something's broken, or if you'd like some specific features added.

License

MIT