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

eslint-config-amo

v5.11.0

Published

Eslint config for amo based projects

Downloads

1,970

Readme

eslint-config-amo

CircleCI npm version

Shared eslint config for all amo related JS projects.

Versioning

This project follows the semantic versioning specification.

In order to release a new version, please follow these steps:

  1. Make sure your local master branch is up-to-date.

  2. Run the following command from the master branch to (1) bump the version accordingly and (2) create a commit and a tag for the release:

    npm version minor

    Note: change minor to patch or major depending on the release (but minor is the most frequent).

  3. Push to the main repository (denoted upstream below):

    git push upstream master --tag
  4. Create a GitHub Release for the new tag: https://github.com/mozilla/eslint-config-amo/releases (you can either select the tag itself or create a new "draft"). Please add a short description of the changes (see the other releases for inspiration).