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

@oazmi/esbuild-types

v0.28.0

Published

this library simply re-exports esbuild's typescript declarations file, so that your client won't have to install esbuild just for its types only.

Readme

@oazmi/esbuild-types

this library simply re-exports esbuild's typescript declarations file, so that your client won't have to install esbuild just for its types only.

rationale

in deno, there is no such thing as devDependencies, so if you write an esbuild-plugin utilizing esbuild's types, deno will download the entirety of the esbuild package from npm, even if you only import your plugin library from jsr.

thus, this library provides a lightweight type-definitions only alternative to npm:esbuild, using the same minor versioning that esbuild uses.

example

your old horizontally-challenged phat code:

import type * as esbuild from "npm:esbuild@^0.24"

export const my_plugin: esbuild.Plugin = {
	name: "my-plugin",
	setup(build: esbuild.PluginBuild) {
		// do plugin related stuff.
	},
}

your new low-phat code:

import type * as esbuild from "jsr:@oazmi/esbuild-types@^0.24"

export const my_plugin: esbuild.Plugin = {
	name: "my-plugin",
	setup(build: esbuild.PluginBuild) {
		// do plugin related stuff.
	},
}

internals

this package updates semi-autonomously via the ./update.ts script. and it uses weekly scheduled github actions to check for an update in npm:esbuild's minor or major version, to update and re-publish accordingly.

to manually bump to the next esbuild minor-version, simply execute the following command in your shell:

deno task update-proj