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-package-config-observer

v0.0.6

Published

A small library for observing a packages config in the Atom text editor

Readme

atom-package-config-observer

A small library for observing a packages config in the Atom text editor.

usage

ConfigObserver = require 'atom-package-config-observer'

class MyAtomPackage
  config: ...

  activate: ->
    # construct new ConfigObserver with your package name
    @configObserver = new ConfigObserver 'my-atom-package'
    # listen for global config changes
    @configObserver.observeGlobalConfig (config) =>
      @updateGlobalConfig config
    @configObserver.observeScopedConfig (config, editors, scopeName) =>
      # config keys not set for this scope are defaulted to global values
      # editors is an array of TextEditor instances associated with this scope
      # scopeName is a string identifying the scope (e.g. 'source.coffee')
      @updateScopedConfig config, editors, scopeName

  deactivate: ->
    @configObserver.dispose()

methods

observeGlobalConfig(callback)

Equivalent to atom.config.observe 'my-package-name', callback with the minor difference that the configuration object passed to the callback is a clone of the object returned by atom.config.observe.

observeScopedConfig(callback)

Observes TextEditor instances using atom.workspace.observeTextEditors to keep track of scopes to track. It then observes the config of each scope, disposing of the observer when no more TextEditors are associated with this scope. The callback has three arguments, see the usage section.

dispose()

Disposes of all registered observers.

configForScope(scopeName)

Returns a clone of the packages configuration object associated with the scope. When values are not set within the scope they are defaulted to the global configuration.

editorsForObservedScopes()

Returns an object with scopeNames as keys and an array of their associated TextEditors as value.

Copyright & License

© Olmo Kramer, 2015 MIT License