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

multi-tool

v0.5.0

Published

Install and require multiple simultaneous versions of any NPM package

Downloads

15

Readme

multi-tool | Install and require multiple simultaneous versions of any NPM package

version versioning branching styling paradigm build

Install multiple versions of NPM packages at runtime. Use any semver ranges which are also a valid (Li|U)nix directory names as your version and require them intuitively (e.g. require('[email protected]'), require('ramda@~0.22.1'), require('ramda@latest')). Leverage custom invalidators to automatically keep installed packages up-to-date.

Install

$ npm install --save multi-tool
$ # OR
$ yarn add multi-tool

Usage

Require:

An options object is required to configure before using, only path is required.

const options = {
  // Path to install against
  path: 'node_modules',
  // Function used to determine if package should be invalidated and reinstalled when already installed
  invalidate: (name, version, age) => age >= Number.MAX_SAFE_INTEGER,
  // Milliseconds to delay when an install is already occurring before reattempting
  delay: 2500,
  // Milliseconds maximum to delay before an install is considered failed if an install is already occurring
  timeout: 60000
};
const install = require('multi-tool')(options);

Install and use latest version:

const installed = await install('ramda', 'latest');
const R = require('ramda@latest');

R.identity(0);

Install and use exact version:

const installed = await install('ramda', '0.23.0');
const R = require('[email protected]');

R.identity(0);

Install and use x-based version:

const installed = await install('ramda', '0.23.x');
const R = require('[email protected]');

R.identity(0);

Install and use tilde-based version:

const installed = await install('ramda', '~0.22.1');
const R = require('ramda@~0.22.1');

R.identity(0);

Install and use caret-based version:

const installed = await install('ramda', '^0.22.1');
const R = require('ramda@^0.22.1');

R.identity(0);

Install invalid package:

const installed = await install('package-doesnt-exist', 'latest');

Install invalid version:

const installed = await install('ramda', '99.99.99');

Custom invalidators:

It is possible to use custom invalidators to customize when multi-tool should assume an already successfully installed package should be reinstalled. This is accomplished via a higher-order function passed as an argument upon require. The invalidator function is executed upon each install. The invalidator function is provided the package name, the package version, and how many milliseconds ago the package at hand was last successfully installed. The invalidator function should return a Boolean value which when true will invalidate the previously successfully installed package and reinstall. The default invalidator behavior is to always invalidate.

Invalidate always:

const invalidate = (name, version, age) => age >= 0;
const install = require('multi-tool')({path: 'node_modules', invalidate});

Invalidate never:

const invalidate = (name, version, age) => age >= Number.MAX_SAFE_INTEGER;
const install = require('multi-tool')({path: 'node_modules', invalidate});

Invalidate only latest versions and only after 10 minutes:

const invalidate = (name, version, age) => version === 'latest' && age >= 600000;
const install = require('multi-tool')({path: 'node_modules', invalidate});

Maintainers