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-amplifyup

v0.1.0

Published

Scaffold an AmplifyUp Next.js project from the starterkit.

Readme

create-amplifyup

Scaffold an AmplifyUp Next.js project from the starterkit.

This package is for starting a project. It is not a dependency of the app. After the app exists, use @amplifyup/cli for amplifyup init and amplifyup push.

npx create-amplifyup my-app
npx create-amplifyup my-app --example blog
npm create amplifyup my-app

npm create amplifyup is the same command. npm inserts the create- prefix and runs this package.

The empty starter is copied first. --example overlays examples/<name> from the starterkit: its definitions folder, sanity/ when present, and src/. The starterkit is always main of amplifyup/starterkit-nextjs, so template changes ship without a new release of this package. --ref downloads a branch, tag, or sha instead.

The new app gets @amplifyup/cli at latest as a devDependency. Dependencies are installed with whichever package manager invoked the command.

| Flag | Effect | | --- | --- | | --example <name> | Overlay examples/<name> from the starterkit | | --name <name> | npm package name for the new app (defaults to the directory name) | | --ref <ref> | Starterkit branch, tag, or sha instead of main | | --organization <id> | Sanity organization id, for examples that create a Sanity project | | --project-name <name> | Sanity project name | | --skip-sanity | Do not create a Sanity project | | --skip-install | Do not install dependencies |

Set AMPLIFYUP_STARTERKIT_PATH to a local starterkit checkout to scaffold from disk instead of GitHub.

Requires Node 20 or newer.