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

nfvm

v0.2.11

Published

Node File Version Manager

Readme

NFVM - Node File Version Manager

Concept

While writing code I often run into problem of fast switching between versions of local files which are ignored by git. This files for security reason can't be in repository or they are individual for each server. So when I want to start/test app in needed config (with specific set of files) the switching process is too slow.

The nfvm tool - is the first try to solve the problem of my daily pain.

Terminology

Pack

Is a set of files for the project or the part of it. Every file in this pack can have as many versions as you want.
For comfort controll of file versioning you can apply version ONLY for the pack. So when version of pack changes, all files in this pack switches to version of pack.

| Parameter | Type | Description | Default Value| |---------------|---------|------------------------------------------|--------------| |name|String|pack name|''| |defaultVersion|String|name of default version|default| |currentVersion|String|name of current version|default| |versions|String[]|array of registered pack versions|[]| |files|File[]|array of File objects|[]|

File

| Parameter | Type | Description | Default Value| |---------------|---------|------------------------------------------|--------------| |filename|String|the name of file in destination folder|''| |destinationPath|String|full path to destination folder|''| |removeFileIfVersionNotExists|Boolean|if true then when file version does not exists removes the old version of file from the destination directory. Otherwise the old version stays.|true| |symlink|Boolean|if true then creates symlink to file version in destination directory instead of replacing it.|true| |versions|FileVersion[]|array of File Version objects|[]|

File Version

| Parameter | Type | Description | Default Value| |---------------|---------|------------------------------------------|--------------| |name|String|file version name (also should be in Pack.versions)|''| |path|String|full path to file|''|

Installing nfvm

$ npm i nfvm -g

CLI Commands

  • init - create local .nfvmrc.json config file
  • create <packname>
    • -f, --file <filename> - create file
    • -v <version> - create version of pack or file
    • -g, --global - create in global
  • remove <packname> - remove pack
    • -f, --file <filename> - remove file
    • -v <version> - remove version of pack or file
    • -g, --global - remove from global
  • set <packname> <version>
    • -g, --global - sets in global
  • list
    • -p, --pack <packname> - files list in pack
    • -g, --global - list from global

Resources

User Guide
TODO List

Examples

Create pack example

nfvm create example

Create version default for pack example

nfvm create example -v default

Create file 1 for pack example

nfvm create example -f 1

Create version default for file 1 for pack example

nfvm create example -f 1 -v default

Remove pack example

nfvm remove example

Remove version default for pack example

nfvm remove example -v default

Remove file 1 for pack example

nfvm remove example -f 1

Remove version default for file 1 for pack example

nfvm remove example -f 1 -v default

Set default version for example pack

nfvm set example default

List of all packs

nfvm list

List of all files in example pack

nfvm list -p example

Config File

Config file name is .nfvmrc.json with structure:

{
  "packs": [{
    "name": "String",
    "defaultVersion": "String",
    "currentVersion": "String",
    "versions": "String[]",
    "files": [{
      "filename": "String",
      "destinationPath": "String",
      "removeFileIfVersionNotExists": "Boolean",
      "symlink": "Boolean",
      "versions": [{
        "name": "String",
        "path": "String",
      }]
    }]
  }]
}