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

fastygo

v0.2.0

Published

Install a FastyGo site once. Versions stay in the project's go.mod.

Readme

fastygo

fastygo installs a site once. After that, versions live in the project's go.mod. There is no project YAML and no packageManager field.

This release installs:

  • github.com/fastygo/framework v0.4.0
  • github.com/fastygo/modules/render v0.1.0 and templ v0.3.1001 as go tool templ
  • optional markdown, view, and a local Codex bbolt binary from github.com/fastygo/backend/cmd/server v0.1.0
  • embedded Codex fixtures through github.com/fastygo/modules/content-json v0.1.0, or an external Codex origin

Targets are local, vps, and vercel. Local and VPS processes listen on 127.0.0.1. Vercel gets a Go Function at api/index.go.

Install the command

Any of these runs the binary packed inside the npm package. The npm version can be newer than the Go tag because npm versions cannot be replaced after publication. The git repository is private, so the package carries the binary instead of downloading the GitHub release.

npx fastygo init . --module github.com/you/shop
pnpm dlx fastygo init . --module github.com/you/shop
yarn dlx fastygo init . --module github.com/you/shop
bunx fastygo init . --module github.com/you/shop

From the Go module:

go install github.com/fastygo/cli/cmd/[email protected]

Linux amd64 and macOS arm64 can also use install.sh. It checks SHA256SUMS and prints the binary path.

If Go 1.25 is missing, init offers to download it into the user cache before it writes the project. --yes accepts that download when stdin is not a terminal.

First site

fastygo init . --module github.com/you/shop --target vps --with codex
fastygo init . --module github.com/you/site --target vercel --content fixtures
fastygo init . --module github.com/you/site --target vercel --content codex
go run ./cmd/site

--content fixtures is the default. It embeds a Codex manifest and the Home entry. --content codex reads an external GoBackend through CODEX_ORIGIN; the token stays out of the repository. --target vercel does not install a local Codex server. Use --with codex only for local or vps.

fastygo init --help lists the flags. A second init stops when go.mod is already there. fastygo add markdown updates that module.