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

@cfpreview/pages-cli

v0.0.4

Published

[Private Beta Preview] Pages CLI

Readme

[Beta] Pages CLI

$ npm install @cfpreview/pages-cli
$ pages dev [directory | -- command]

Examples

Create React App

$ pages dev --proxy 3000 -- npx react-scripts start

A static folder

$ pages dev ./public

Options

| Name | Description | Default | | ---------- | ----------------------------------------------------- | ------------------------------------------------------- | | --port | The port to listen on. | 7000 | | --proxy | The port to proxy requests for env.ASSETS.fetch to. | Automatically determined by inspecting command process. | | --config | The path to the beta configuration file. | ./pages-functions-beta.json |

Miniflare

Inside your pages-functions-beta.json file, you can add a "miniflare" object which is passed into the constructor of Miniflare:

{
  "entryPoint": "./functions",
  "baseURL": "/",
  "miniflare": {
    "kvPersist": true,
    "kvNamespaces": ["MyKVNamespace"]
  }
}

You can use this to enable environment variables and secret bindings, custom build commands for single Worker setups, KV, and Durable Objects.

Note: this is only for local development and has no impact on any production settings.

Roadmap

  • [ ] Improve help message (the -- command option presents weirdly)
  • [x] Auto-configure --proxy based on command run
    • [x] Testing on Windows
  • [x] Bindings
  • [x] Custom build scripts for single Worker setups