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-get-run

v2.0.0

Published

get specific node versions, including nightly builds, and run them

Downloads

11

Readme

node-get-run

node-get-run installs specific versions of node, either nightlies or released versions, in a local folder.

Install

$ npm install --global node-get-run

Usage

For the first time:

$ node-get-run --release v12.0.1
{status: installed}

And then just use node-get-run as if it were node:

$ node-get-run --inspect --debug-brk index.js

or

$ node-get-run index.js

Installation options

  1. node-get-run --nightly {version} Install a specific nightly, e.g., v12.0.0-nightly20181024bb79e768e5
  2. node-get-run --release {version} Install a specific version, e.g., v12.0.0
  3. ~~node-get-run --upgrade Install the latest nightly~~ (tbd)
  4. ~~node-get-run --clean Delete the currently installed version~~ (tbd)

Clean-up

To delete node-get-run's currently installed version of node just rm -rf .node-get-run.

Credit

This is a derived from node-nightly, from which I got the idea. I changed it to enable a nightly, version, or release to be specified as opposed to just a nightly. I also removed the ability to just fetch the latest nightly until I think it through. I'm not sure how --upgrade should interact with the version relative to the version currently installed, e.g., if node v10.15.1 is installed does --upgrade mean upgrade to a more current version of node 10 or the next node 10 nightly past v10.15.1 or the latest nightly regardless of the node version currently installed.

License

MIT © Hemanth.HM