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

@faststats/sourcemap-uploader-plugin

v0.5.3

Published

> [!IMPORTANT] > This package is in early development and not intended for production use. > It is only published for internal testing.

Readme

@faststats/sourcemap-uploader-plugin

[!IMPORTANT] This package is in early development and not intended for production use. It is only published for internal testing.

Unplugin-based sourcemap uploader that works across all unplugin adapters:

  • Vite
  • Rollup
  • Rolldown
  • Webpack
  • Rspack
  • esbuild
  • Unloader
  • Farm
  • Bun

What it does

  • injects build metadata into entry chunks at globalThis.__SOURCEMAPS_BUILD__ (esbuild injects it into every output file)
  • uploads generated sourcemaps to a backend endpoint
  • uses a custom buildId, the commit hash from CI or git, or a random ID
  • optionally deletes sourcemap files after successful upload

Usage

Create an API key under Project settings → Sourcemaps and pass it to the plugin:

import sourcemapsPlugin from "@faststats/sourcemap-uploader-plugin/vite";

export default {
  build: { sourcemap: true },
  plugins: [
    sourcemapsPlugin({
      authToken: process.env.FASTSTATS_SOURCEMAP_KEY,
      deleteAfterUpload: true,
    }),
  ],
};

Every bundler has its own entry point: /vite, /rollup, /rolldown, /webpack, /rspack, /esbuild, /unloader, /farm and /bun.

Options

  • authToken: FastStats API key scoped to one project with the sourceMap:upload permission
  • endpoint: upload URL, https://sourcemaps.faststats.dev/v0/upload by default
  • enabled: true by default; set false or pass (framework) => boolean to disable the plugin conditionally
  • buildId: custom build identifier; defaults to the commit hash from CI or git
  • maxUploadBodyBytes: largest request body the plugin sends, 50 MB by default; builds are split into requests of about 8 MB (or this limit, if lower) that upload four at a time
  • failOnError: true by default; set false to let the build succeed when the upload fails
  • deleteAfterUpload: remove sourcemap files after successful upload
  • globalKey: runtime global key for build metadata
  • fetchImpl: custom fetch implementation
  • onUploadSuccess: callback after each uploaded request; requests complete in any order
  • onUploadError: callback when upload fails

Upload payload

The plugin sends POST /v0/upload with this JSON body:

{
  "type": "javascript",
  "buildId": "build-123",
  "uploadedAt": "2026-04-01T12:00:00.000Z",
  "files": [
    {
      "fileName": "assets/app.js.map",
      "content": "{...}"
    }
  ]
}

Tests

bun run test