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

node-engines

v1.0.1-c

Published

engines package builder

Downloads

9

Readme

Welcome to node-engines 👋

Version Documentation Maintenance License: MIT

Node engines package builder

Homepage

🏠 Homepage

Node Engines

Node Engines is a command-line tool that helps developers automatically detect and update the Node.js and npm versions in their project's package.json file; useful when working with NVM.

Installation

You can install the Node Engines package globally using npm:

npm install -g node-engines

Usage

After installing the package, you can use the node-engines command from any directory where you have a package.json file to detect and update the Node.js and npm versions.

Here's how you can use it:

node-engines

Running the node-engines command will perform the following actions:

  1. Detect the current Node.js version installed on your system.
  2. Detect the current npm (Node Package Manager) version.
  3. Update the engines field in your project's package.json to specify the detected Node.js and npm versions.

If the package.json file does not exist in the current directory, the tool will display an error message.

Example

Before running node-engines, your package.json may look like this:

{
  "name": "my-node-app",
  "version": "1.0.0",
  "engines": {
    "node": ">=12.0.0",
    "npm": ">=6.0.0"
  },
  // ...
}

After running node-engines, your package.json will be updated with the detected versions:

{
  "name": "my-node-app",
  "version": "1.0.0",
  "engines": {
    "node": ">=14.17.5",
    "npm": ">=7.24.0"
  },
  // ...
}

Run tests

npm run test

Author

👤 Jason Mullings [email protected]

  • Website: https://jasonmullings.com/
  • Github: @jmullings

Contributing

Contributions, issues and feature requests are welcome!

Feel free to check issues page. You can also take a look at the contributing guide.

Show your support

Give a ⭐️ if this project helped you!

License

This project is MIT licensed.