npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2023 – Pkg Stats / Ryan Hefner




Vendored dependencies for Victory





Vendored dependencies for Victory.


D3 has released most of its libraries as ESM-only. This means that consumers in Node.js applications can no longer just require() anything with a d3 transitive dependency, including much of Victory.

To help provide an easy path to folks still using CommonJS in their Node.js applications that consume Victory, we now provide this package to vendor in various d3-related packages.


We presently provide the following top-level libraries:

  • d3-ease
  • d3-interpolate
  • d3-scale
  • d3-shape
  • d3-timer

This is the total list of top and transitive libraries we vendor:

  • d3-array
  • d3-color
  • d3-ease
  • d3-format
  • d3-interpolate
  • d3-path
  • d3-scale
  • d3-shape
  • d3-time
  • d3-time-format
  • d3-timer
  • internmap

Note that this does not include the following D3 libraries that still support CommonJS:

  • d3-voronoi

How it works

We provide two alternate paths and behaviors -- for ESM and CommonJS


If you do a Node.js import like:

import { interpolate } from "victory-vendor/d3-interpolate";

under the hood it's going to just re-export and pass you through to node_modules/d3-interpolate, the real ESM library from D3.


If you do a Node.js import like:

const { interpolate } = require("victory-vendor/d3-interpolate");

under the hood it's going to will go to an alternate path that contains the transpiled version of the underlying d3 library to be found at victory-vendor/lib-vendor/d3-interpolate/**/*.js. This futher has internally consistent import references to other victory-vendor/lib-vendor/<pkg-name> paths.

Note that for some tooling (like Jest) that doesn't play well with package.json:exports routing to this CommonJS path, we also output a root file in the form of victory-vendor/d3-interpolate.js.


This project is released under the MIT license, but the vendor'ed in libraries include other licenses (e.g. ISC) that we enumerate in our package.json:license field.