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

@logfrog/cli

v0.1.0

Published

Build and upload private JavaScript source maps to Logfrog.

Readme

Logfrog CLI

Build a React app with private production source maps and upload them to the selected Logfrog project.

Install

npm install --global @logfrog/cli
logfrog login

Login opens Logfrog in your browser, asks which projects the CLI may access, and stores refreshable credentials in ~/.config/logfrog/config.json with user-only permissions. Passwords never pass through the CLI.

Vite / React

Make the runtime release use the value injected by the CLI:

logfrog.init({
  release: import.meta.env.VITE_LOGFROG_RELEASE,
  features: { updates: true, feedback: true },
});

Then run this from the React repository:

logfrog upload

For Vite, the CLI runs the existing build script with --sourcemap hidden. It also supports Create React App and existing generic JavaScript source maps. The default release is <package-version>-<git-sha>.

Useful options:

logfrog projects
logfrog use "My project"
logfrog upload --release 2.4.0-abc123
logfrog upload --no-build --dir dist
logfrog upload --delete-after-upload
logfrog upload --dry-run

--delete-after-upload removes only the .map files that were successfully uploaded. Use it when the build directory is deployed directly and maps should not be published.

For CI, run logfrog login once in a protected environment and preserve the CLI config directory as a secret, or set LOGFROG_CONFIG_DIR to a protected mounted directory.