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

filemaker-cli

v0.1.3

Published

A cross-platform CLI tool to scaffold files and folders instantly from a list or a structure.txt blueprint.

Readme

filemaker-cli

A cross-platform CLI tool that scaffolds files and folders instantly, either from a structure.txt blueprint or an interactive prompt.

Installs as filemaker-cli, runs as filemaker.

Install

npm install -g filemaker-cli

Usage

cd any/project/folder
filemaker

If a structure.txt file exists in the current directory, filemaker reads it and builds everything listed, line by line. Otherwise it asks what you want to build.

filemaker --dry-run     show what would be created without touching disk
filemaker --version     print the installed version
filemaker --help        show usage info

structure.txt format

src/
src/index.js
src/utils/helpers.js
.env
.gitignore
LICENSE
README.md

One entry per line. Lines ending in / are always folders. Anything starting with a dot, like .env or .gitignore, is always a file. Names with a real extension are files too. A handful of common extension-less filenames (LICENSE, Dockerfile, Makefile, README, CHANGELOG, and similar) are recognized as files as well. Everything else is treated as a folder. Blank lines and lines starting with # are ignored.

Comma mode example

What do you want to build? (Separate items with commas)
> src/, src/index.js, .env, .gitignore, README.md

Safety

filemaker only ever creates things inside the folder you ran it from. Any entry that tries to escape that folder (using ../ or an absolute path) gets skipped and reported, not silently followed.

Running filemaker again over an existing structure won't overwrite anything. Items that already exist are left alone and marked "[already there]".

Exiting

Press Ctrl+C at any time to exit cleanly:

Closing safely... Take care!