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

@wndrfl/static-kit-cli

v2.11.0

Published

A commandline interface for compiling, optimizing, and managing static assets.

Readme

✨ Static Kit CLI

A commandline interface for bootstrapping and working with Wonderful's Static Kit library.

Table of Contents

  1. Documentation
    1. Quick Start
    2. Installation
    3. Commands
    4. Directory Structure
    5. Configuration
    6. Testing
  2. Support
  3. Known issues
  4. License

Documentation

Quick Start

After installing the CLI, you can get started with just two commands:

# Install Static Kit into your project
$ static install

# Start watching for changes and compiling automatically
$ static -w

That's it! The CLI will watch your source files and automatically compile them whenever you make changes.

Installation

Using npm:

# Install the CLI globally
$ npm install -g @wndrfl/static-kit-cli

# Update to the latest version
$ npm update -g @wndrfl/static-kit-cli

# Check the current version
$ static version

Commands

The Static Kit CLI provides different commands for many common tasks, as they pertain to interfacing with the Static Kit library.

static install [-d --dir] [-i --init]

Installs the Static Kit library into the current directory (or, optionally, a directory indicated by the --dir flag). If the --init flag is provided, the CLI will automatically run commands such as npm install within the new installation.

static compile [all|js|css|images] [-d --dir] [-w --watch]

Compiles source Javascript, CSS (SCSS), and image files into distributable files. The command uses the .staticrc file to understand where to find the source files and where to output the distribution files.

Options:

  • -w, --watch: Watch for changes and automatically recompile files (recommended for development)
  • -d, --dir: Specify the directory to compile from (default: current directory)

Examples:

# Start watching for changes (recommended for development)
$ static -w

# Compile all assets once
$ static compile

# Compile specific asset types
$ static compile js
$ static compile css
$ static compile images

# Compile from a specific directory
$ static compile --dir ./my-project

static template [create] [-n --name] [-d --dir]

Creates a pair of .js and .scss files within the Static Kit directory. Use this command when beginning work on static assets (JS / CSS) for a new page template.

Directory Structure

When you run static install, it creates a static directory with the following structure:

static/
├── .staticrc           # Configuration file for the CLI
├── src/               # Source files
│   ├── js/           # JavaScript source files
│   ├── scss/         # SCSS source files
│   └── images/       # Image source files
└── dist/             # Compiled output files
    ├── js/          # Compiled JavaScript
    ├── css/         # Compiled CSS
    └── images/      # Optimized images

Configuration

The CLI uses a .staticrc file to configure compilation settings. Here's an example configuration:

{
  "paths": {
    "src": {
      "js": "src/js",
      "scss": "src/scss",
      "images": "src/images"
    },
    "dist": {
      "js": "dist/js",
      "css": "dist/css",
      "images": "dist/images"
    }
  },
  "overwrite": false
}

Configuration options:

  • paths: Define source and destination directories for different asset types
  • overwrite: When false (default), the dist directory is emptied before each compilation. Set to true to preserve existing files.

Testing

The CLI includes a test suite that verifies the installation and compilation process. To run the tests:

$ npm run test

The test suite:

  1. Creates a test directory
  2. Installs Static Kit
  3. Compiles the assets
  4. Verifies the compilation output
  5. Cleans up the test directory

Support

The CLI has been tested on the following tools. Please let us know if how it works in your environment!

  • Mac OS:
    • Terminal.app
    • iTerm
  • Windows:
    • (needs testing, please let us know how it works!)
  • Linux:
    • (needs testing, please let us know how it works!)

Known Issues

Currently there are no known issues. However, if you experience something, we certainly want to know! Please submit a Github issue.

License

Copyright (c) 2025 Wonderful Licensed under the MIT license.

Collaborators