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

navcare.reactcontrols

v1.5.39

Published

common react controls to be used accross the navcare ecosystem ()public

Readme

NaveCare.Controls

common react controls

  1. build to check for errors: npm run-script build
  2. transpile: ./node_modules/.bin/babel src --out-dir _dist --copy-files
  3. commit all pending changes to git
  4. login to npm: npm login and then enter npm https://www.npmjs.com/ credentials
  5. install np: npm install --global np
  6. publish using np: np --any-branch --no-tests -no-2fa --branch develop

finally: 5) Update the package in you consuming project using: npm update navcare.reactcontrols

//-------------------------------------------------------------------------

DEBUGGING

  • to debug this node package in your application without publishing/updating, you need to create a symlink (temporarily replacing use of npm pakcage with local package)
  1. in the root of this (navcare.reactcontrols) project run npm link. this will create a symlink

  2. in your consuming project, run npm link navcare.reactcontrols. this will replace your npm package (in node_modules) with a symlink to this project to be used directly.

  3. always run ./node_modules/.bin/babel src --out-dir _dist --copy-files here before rebuilding your consuming project to use latest changes.

NOTE: Whenever you run npm install or npm update in the consuming project, it will destroy the symlink and replace it with the npm package- if you want to re-add the symlink in that project, just run step 2 again.