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

@zuplo/editor

v1.0.33901066608

Published

Local development editor for the Zuplo CLI

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

ntottenntottenzuplo-integrationszuplo-integrationsvazexqivazexqi

Keywords

zuplo

Readme

Zuplo Editor

This project is not meant to be used independently. It is part of the Zuplo CLI

Publishing

The published package is publish/, not this directory.

pnpm --filter @zuplo/editor build:package
npm publish ./packages/editor/publish

This directory is a workspace member, so publishing it directly would ship the spec files and a dependencies list containing everything the editor imports. build:package assembles the real artifact instead: every runtime dependency is bundled and tree-shaken, only the declarations reachable from the entry points are copied, and the package.json is generated from scratch. The published package has no dependencies — see scripts/build-package.ts.

That last part is why EditorApp.fetch is a plain function and AssetSource.serve takes a Request, rather than the Hono and hono Context they really are: a published declaration can only name a type a consumer can resolve, and hono is bundled. The build fails if a reachable declaration names anything that isn't installable, so this can't regress quietly.

npm publish from this directory fails on purpose.