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

@codeserk/forge-stats-vite

v0.7.0

Published

Vite plugin for Forge Stats. Uploads the source maps of the build, so errors show the original code.

Readme

@codeserk/forge-stats-vite

Vite plugin for @codeserk/forge-stats. Builds with hidden source maps, uploads them in the compact format to the public API after the build and deletes them from the output, so they are never deployed. Errors are then resolved to the original code. A failed upload only warns, the build passes.

Installation

npm install --save-dev @codeserk/forge-stats-vite

Usage

The SDK key comes from the env var tokenEnv names. Use the key of a CI client with the upload-sourcemaps permission, never the one the app ships, and do not prefix the var with VITE_, so it stays out of the bundle:

import { defineConfig } from 'vite'
import { forgeStats } from '@codeserk/forge-stats-vite'

export default defineConfig({
  plugins: [forgeStats({ appVersion: process.env.APP_VERSION!, tokenEnv: 'FORGE_STATS_CI_SDK' })],
})

Use the same appVersion in init, so errors are resolved with the source maps of their build.

| Option | Type | Description | | ------------ | -------- | ---------------------------------------------------------------------------- | | appVersion | string | Version of the build | | tokenEnv | string | Name of the env var with the SDK key of the CI client | | baseUrl | string | Optional. Base URL of the public API. Defaults to https://api.forge.codeserk.es |