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

nuclide-atom-npm

v0.0.35

Published

Utility to load an Atom package that is packaged as a Node package

Readme

nuclide-atom-npm

Package to register Atom-specific Node packages.

This global registry prevents Node packages from triggering side effects multiple times (e.g. adding stylesheets, registering keybindings). Note that this also prevents different Atom packages from using different versions of the Node package.

Register a Node package

The first argument is the root path of your package's code (the path to lib/).

The second argument is the path to what you'd normally put in main.js. This value also functions as a key -- calling require() on the package will return the first package that was registered with this key.

This approach prevents Node from having to evaluate the implementation multiple times and allows it to load resources from styles/ and grammars/. (Other directories, such as menus/ and keymaps/, are future work.)

module.exports = require('nuclide-atom-npm').load(__dirname, 'AtomInput');

Use the Node package

Add the dependency in package.json as usual:

{
  "name": "nuclide-buck-toolbar",
  "engines": {
    "atom": ">0.193.0"
  },
  "dependencies": {
    "nuclide-ui-atom-input": "0.0.0",
  }
}

Require the package as usual:

var AtomInput = require('nuclide-ui-atom-input');

module.exports = React.createClass({
  render() {
    return <AtomInput />;
  },
});