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

node-version-call-local

v1.1.6

Published

Call a function in a Node version found in PATH

Downloads

282,272

Readme

node-version-call-local

Call a worker function with a Node.js version already available in PATH. It does not install Node.js versions. Use node-version-call when installation is required.

Install

npm install node-version-call-local

Worker

The worker file must export a function. For example, worker.cjs can contain:

module.exports = function (value) {
  return process.version + ': ' + value;
};

Usage

import { fileURLToPath } from 'url';
import { bindSync, bind } from 'node-version-call-local';

const workerPath = fileURLToPath(new URL('./worker.cjs', import.meta.url));

const syncWorker = bindSync(process.version, workerPath);
console.log(syncWorker('sync'));

const asyncWorker = bind(process.version, workerPath);
console.log(await asyncWorker('async'));

asyncWorker('callback', (err, result) => {
  if (err) throw err;
  console.log(result);
});

Use callSync(version, workerPath, options?, ...args) or call(version, workerPath, options?, ...args) for one-off calls. The version is a semver constraint such as '>=18', '^16', or 'v18.0.0'. If no matching Node executable is available in PATH, the call fails.

API

  • bindSync(version, workerPath, options?) returns a synchronous caller. It throws worker errors.
  • bind(version, workerPath, options?) returns a caller that supports a callback or a Promise.
  • callSync(version, workerPath, options?, ...args) performs one synchronous call.
  • call(version, workerPath, options?, ...args) performs one callback or Promise call.

options.callbacks: true tells the library that the worker expects fn(...args, callback) instead of returning a value or Promise. spawnOptions defaults to true and updates the child process environment so nested commands use the selected Node installation. Use env for custom environment variables, moduleType to select module detection, and interop to control ESM default-export handling.