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 🙏

© 2025 – Pkg Stats / Ryan Hefner

deploy-nextjs-example-app

v0.0.4

Published

Deploys a [Next.js](https://nextjs.org/docs) library's `./example` app on [now.sh](https://zeit.co/docs).

Readme

Deploy Next.js Next.js example app

Deploys a Next.js library's ./example app on now.sh.

The app is copied to a temporary directory where it is prepared before now is invoked. The main purpose of this script is to workaround Next's inability1 to work with symlinked (or file:.. dependencies when deployed to now.

Install

yarn global add deploy-nextjs-example-app

Usage

deploy-nextjs-example-app

To also run now ln also an --alias CLI flag can be used

deploy-nextjs-example-app --alias

Is this really necessary?

This seems necessary based on my experience (see summary above) but I would be excited to learn that I'm wrong and there's an easy way to do deploy a Next.js app to now.sh that lives in a repo subdirectory and depends on another npm package located in the same repo. Please reach out to me at [email protected] if you can help, thanks!