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 🙏

© 2025 – Pkg Stats / Ryan Hefner

folder-npm

v0.0.2

Published

offline node module installer

Readme

Folder-NPM

Features


  • Module management between folders is possible

  • It's easy to manage with private projects

  • Available with folder path and simple json creation

Installation


npm install folder-npm

How to use


Prepare modue project A to be used first and project B to be applied

Create a "fnpm.json" file in Project A and write the following

//fnpm.json
{
    "ignore":[
        "node_modules/",
        ".git",
        "fnpm.json",
        "package-lock.json",
        ".gitignore"
        //===================================
        //Specify files/folders to exclude
        //===================================
    ],
    "dependencies":{}
}

(How to write ignore)

| Option | Description | | ------ | ----------- | | path | Remove only matching files/folders. ex) path, path/temp | | path/ | Remove only matching folders. ex) path/, temp/path/,path/temp | | /path | Remove only the files/folders that match from the beginning of the absolute path. ex) path, path/temp (not temp/path)| | *.~ | Exclude all applicable extensions. ex) *.zip, *.json |

Go to project B, install "npm install folder-npm"

and make and wrtie script file, like the bottom

//install.js (Write the file name as comfortable as you like)

const fnpm=require('folder-npm')

fnpm.FromParentPath('{folder name of the A project}')
or
fnpm.Path('{path of the A project}') //C:\~
...(Add another module if present)

fnpm.Install()
"FromParentPath" search by the folder name of Project A in the top folder of Project B
"Path" search by the absolute path of Project A
"Install" It's a function that actually installs it

Finally, run "node install.js" in the terminal(command)