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

@nodesource/ncm-project

v3.1.0

Published

Set up a NCM project

Downloads

4

Readme

Usage

While NCM will work for any npm install on your system, it works at its best when it knows which project a npm install call belongs to. Therefore this module, ncm-project, creates or extends a .npmrc in your project folder and sets the registry value to your local NCM Desktop instance. All following npm install calls in this project will then be handled by NCM. Please make sure you're always running NCM Desktop for uninterrupted operation:

$ cd my-project
$ npm install --save @nodesource/ncm-project

The created .npmrc file should then be committed and therefore used by the whole team:

$ git add package.json package-lock.json .npmrc
$ git commit -m 'add NCM'

That's it, now just tell your teammates to run NCM Desktop too (if they don't do so already) and your project is fully configured for NCM!

Troubleshooting

If your npm install times out (ENOTFOUND) or just hangs without any explanation, please make sure your NCM Desktop app is up and running, and maybe restart it too.

Development

  1. Clone this repository and run npm install
  2. Create a temporary project
  3. Inside that project, run npm install file:PATH-TO-THIS-REPOSITORY-ON-DISK

License

MIT