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 🙏

© 2026 – Pkg Stats / Ryan Hefner

atom-blitz-settings

v0.0.3

Published

Repair erronous settings for an atom package

Downloads

11

Readme

atom-blitz-settings

Have you ever renamed your atom package or renamed/moved a package setting? If so you have likely noticed that atom does not remove those stale values from the config.cson file. This can lead to extra entries within the settings view and bugs within your own code.

This module allows an atom package to resolve these erroneous settings.

Install with

npm install --save
Usage

Within your packages activate method, add a call similar to:

import blitz from 'atom-blitz-settings'

activate () {
    blitz('my-package-name', (key, value) => {
        if (key in myOldConfigKeys) {
            atom.config.set('new-config-key', value)
        }
    })
}
blitz (packageName, handler)
  • packageName [String | Array<String>] (optional)
    If not given, will deduce the name from the call stack adding to your package load time. For best results always pass your package name. Multiple package names may be given allowing you to migrate settings from a renamed package into the new config namespace.
  • handler [Function] (optional)
    If given, will be called with all erroneous config keys and their values. If not given all keys will be removed from config.cson. Returning a falsy will remove the key, if you wish to leave the key intact be sure to return true.