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

cewb

v0.2.1

Published

Build Chrome Extensions with Webpack + Babel

Downloads

5

Readme

cewb

Build Chrome Extensions with Webpack + Babel

Features

  • 🏗 Next generation ES features with babel
  • ⛓ Code bundling with webpack
  • 🔁 Live reload on source change
  • 📦 Packs your extension into a zip

Installation

npm install --dev cewb
# or
yarn add --dev cewb

Usage

Example directory structure:

  + /project-directory
  |-+ /assets
  | '-- /icon.png
  |-- /manifest.json
  |-- /package.json
  |-+ /src
  | |-- /background.ext.js
  | |-- /utils.js
  | '-- /injectedScript.ext.js
  '-- /webpack.js

Example package.json:

{
  "name": "my-extension",
  "scripts": {
    "dev": "cewb",
    "prod": "cewb -p"
  }
}

File naming

Any file that ends with .ext.js will be added to webpack's entries object and therefore will be accessible by manifest.json.

Customize webpack configuration

Example webpack.js:

module.exports = (config, env) => {
  if (env === 'development') {
    config.plugins.push(new WebpackPlugin())
  }

  return config
}

Development

Running npm run dev will take all the static assets, transpile all source files, output these files to a directory named unpacked and then watch all files under src for live reloading.

After you've run npm run dev for the first time, goto chrome://extensions in Chrome, ensure "Developer mode" is checked, click "Load unpacked extension...", locate and select your extensions unpacked folder and you're ready to go!

Production

Running npm run prod will do everything npm run dev does but instead of outputting files to unpacked, it packages the extension into <package-name>.zip file.