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

@myandrienko/nextpage

v2.1.0

Published

Project scratchpad

Readme

Bootstrapping new projects comes with some friction. Even if it only takes a couple of commands, taking the time to come up with a project name or waiting for packages to install can disrupt your flow.

If you regularly create scratchpad projects using the same template, it's helpful to always have an empty project ready.

That's what nextpage does: it prepares a spare project for you, so it's ready when you need it. You can start working immediately while another spare project is bootstrapped in the background.

Quick Start

Run the nextpage to initialize the current directory:

npx @myandrienko/nextpage

A .nextpage subdirectory is created with the default configuration:

.nextpage
├ template     ← project structure
│ └ README.md
├ open         ← launch an editor, IDE...
└ prepare      ← install dependencies

Run nextpage again to bootstrap and open your first project:

npx @myandrienko/nextpage

A spare project is also created.

Slightly Slower Start

Install globally from npm:

npm install -g @myandrienko/nextpage
pnpm add -g @myandrienko/nextpage

Run the nextpage command in the directory where you store your scratchpad projects:

nextpage

This will initialize the scratchpad directory by adding the .nextpage subdirectory:

.nextpage
├ template
│ └ README.md
├ open
└ prepare

Running the nextpage command again at this point will bootstrap and open your first project (using the default template) and prepare a spare project.

You can configure how the project opens and customize the bootstrapping process by editing the files in the .nextpage subdirectory.

Configuration

The open script opens a prepared project. In this script, you probably want to launch your favorite editor or IDE. You may also want to execute additional commands, like launching a dev server:

.nextpage/open:

#!/usr/bin/env bash
code . # open project in vscode
npm run dev # start dev server

When this script is executed, cwd is the prepared project's directory. The randomly generated project name is also passed to the script via the $NEXTPAGE environment variable, though you likely won't need it.

The prepare script contains the bootstrapping steps. It is used to prepare a spare project. First, the .nextpage/template directory is used to create a new directory with a randomly generated name. Then, the prepare script is executed in this directory.

For example, for a Node project you might want to have a template with a package.json file and install dependencies in the prepare script:

.nextpage
├ template
│ └ package.json
├ open
└ prepare

.nextpage/prepare:

#!/usr/bin/env bash
npm install

Ensure that the open and prepare files are executable; otherwise, they will be ignored.

Since the bootstrapping steps are executed in advance, there's always a randomly named spare project prepared. Its name is stored in the .nextpage/next file. Do not edit this file manually.