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

pwinruninnodeversion

v0.1.2

Published

Program to run another Node.js program in any version of Node.js on Windows

Downloads

5

Readme

pWinRunInNodeVersion

Program to run a script in any processor architecture and version of Node.js on Windows

Getting Started

  1. Install pWinRunInNodeVersion globally via NPM.

npm install pwinruninnodeversion -g

Optionally: rename pwinruninnodeversion to pWinRunInNodeVersion: npm is unable to handle the complexity of uppercase characters in a module name. Node.js on Windows does not have this problem, so renaming the folder is not required for you to use the module.

  1. Run your script in a specific Node.js processor architecture and version.

node-ia32 0.9.9 your-script arguments... node-x64 0.12.0 your-script arguments...

Notes

Usage

This program provides two short cuts: node-ia32 and node-x64 (and two aliases: node-x86 and node-amd64 respectively) that allow you to run the 32- and 64-bit versions of Node.js. Note that you must be running a 64-bit version of Windows to run a 64-bit version of Node.js.

The first argument passed to these scripts must be a version number. This may or may not contain a patch number, eg. (0.9.9, 0.9, 0.9.x) If a patch number is provided, that exact version of Node.js will be used. If no patch number is provided, any cached version of Node.js that has the requested mayor and minor version number will be used. If no such version is cached, the patch level 0 will be used (eg. 0.9.0 in this example).

In order to run the script, the relevant stand-alone node.exe binary is downloaded over a secure connection from node.js.org Is is cached in a sub-folder of the bin/ folder of your pRunInNodeVersion installation. The next time you want to run a script in the same version, the cached version will be used.

All arguments passed after the version number will be passed to node.exe, so you can do:

C:\>node-x86 0.10.10 -v
0.10.10

C:\>

License

This code is licensed under CC0 v1.0 Universal.