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

@offliner/npm2stage-v9.5.1

v1.0.0

Published

CLI to manage npm-two-stage installation for npm 9.5.1

Downloads

4

Readme

@offliner/npm2stage-v9.5.1

CLI to manage npm-two-stage installation for npm 9.5.1

Installation

$ npm install -g @offliner/npm2stage-v9.5.1

Usage

The npm installation that is to be the target of this tool's commands must have the targeted version. If it doesn't match, the tool will tell you so, and it will not operate on it.

In these examples, the OS is Windows, the tool is used in a git bash console, and the target location is the typical global installation location. However, the tool (and npm-two-stage) are platform-agnostic, and the target npm installation can be any accessible location, including on a removeable drive.

$ npm2stage status

    Checking npm version at given path...
    Target npm home is C:\Program Files\nodejs\node_modules\npm
    No backups present.
    No standard files missing.
    No new files present.
    npm-two-stage is not installed at this location.

At this point, it's appropriate to run npm2stage install.

$ npm2stage install

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Backing up files to be replaced:
     # (original files listed here)
   Copying into target directory:
     # (replacements and new files/dirs listed here)

   Installation of npm-two-stage was successful.

At this point, npm download and npm install --offline are ready to be used.

$ npm2stage status

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   All backups present.
   No standard files missing.
   All expected new files present.
   npm-two-stage is fully installed at this location.

At this point, you may run npm2stage uninstall (if you must).

$ npm2stage uninstall

   Checking npm version at given path...
   Target npm home is C:\Program Files\nodejs\node_modules\npm
   Removing items added by npm-two-stage install:
     # (replacements and new files/dirs listed here)
   Restoring backed-up original files...
     # (original files listed here)
    
   Removal of npm-two-stage was successful.

For the install and uninstall commands, there are the abbreviations that the power user of npm will be familiar with: i and un. Also for these two commands, there is the --silent option to mute output unless there is an error.

For help:

$ npm2stage help

...or specifically for a command:

$ npm2stage install -h