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

create-yaspp

v1.1.12

Published

Yaspp project generator

Readme

create-yaspp

Package for creating a Yaspp web site

To use this package, you do not need to install it. Simply cd to the folder in which you want to create your yaspp project (preferably an empty one) and run the command npx create-yaspp. You can also specify a different project folder. Note that the script will not proceed if the project contains a file/folder named like an asset that create-yaspp needs to copy.

$ npx create-yaspp [...arguments]

Command line options

Runtime Options

  • --dryrun: Dry run. Print all the steps.
  • --auto: If the configuration process involves interaction with the user, then create-yaspp will use the values provided in the command line without prompting the user for input.
  • --target <path/to/target/folder>: absolute or relative path of the folder in which the project will be created. Defaults to current working directory. The target directory should not contain any file or folder named like an asset that the script needs to create.
  • --no-install: Don't make the sample site publish-ready by running the initialization scripts in it. You can perform this step yourself by running yarn init-clean or yarn init-site in the created project folder.
  • --verbose: Print edifying messages in each step of the project setup.

Install procedure

The rest of this document uses the yarn command. You can replace it with your favorite package runner, e.g. npm run .... However, the tool itself requires yarn to run properly.

After the command line options are validated, create-yaspp performs the following actions:

  1. Create a sample site under the project folder, including sample data and valid configuration files.
  2. if no-install was not specified, run yarn init-clean in the project folder. This will clone the Yaspp repository into the yaspp folder and setup the yaspp platform by running the required scripts there.

Post install

Note: If you save the result of this setup in a git repository, always make sure that the file yaspp/README.md is present. This file Doesn't serve any purpose in the site, but it's needed just to keep the yaspp folder in the repository. Without it, deployment on Vercel fails.

See the Yaspp project for details about building and publishing a yaspp site. If the installation completed successfully, you should be able to test your site by running yarn dev in the project root or in the yaspp folder.