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

package-node-to-nvmrc

v0.0.3

Published

Keep your .nvmrc file upto date with your package.json node engine

Downloads

7

Readme

Install

npm i -D package-node-to-nvmrc

Description

package-node-to-nvmrc was designed to run as part of a pre-commit hook to avoid the lack of consistency caused by the need to manually keep this:

// package.json
{
  "engines": {
    "node": "14.17.0"
  }
}

and this, in sync:

# .nvmrc
14.17.0

Usage

We recommend using husky v6 to do this. Once you have installed husky, create a pre-commit hook in your project line with their documentation.

Navigate to the pre-commit file (inside a .husky directory in v6) and add the following line to the file npx package-node-to-nvmrc && git add .nvmrc.

An example of a full file with only this package to be run would look like:

#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

npx package-node-to-nvmrc && git add .nvmrc

Ensure you have your engine declared in package.json, and commit your changes. You should see an .nvmrc is generated, added and committed as part of the process.