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

@figureit/editor

v0.5.1

Published

Framework-independent FigureIt editor Web Component.

Readme

@figureit/editor

The FigureIt editor as a web component. Drop <figureit-editor> into any page, framework or none.

FigureIt comes from figure it out. You draw what you are thinking, see it, arrange it, and understand it in the arranging — and this is the surface where that happens.

npm install @figureit/editor
<figureit-editor id="editor"></figureit-editor>
<script type="module">
  import "@figureit/editor";

  const editor = document.querySelector("#editor");
  editor.source = `figure { schemaVersion: 1; }`;

  editor.addEventListener("figureit-change", ({ detail }) => {
    console.log(detail.source); // canonical text, ready to store
  });
</script>

The contract

It never writes anything. Not a file, not a request. It holds a document, tells you when it is dirty, and hands you canonical text when asked — where a figure belongs is your decision, and an editor that guessed would be wrong somewhere. Answer save-request with acknowledgeSave, reportSaveError, reportConflict, or abandonSave.

It stays inside its element. A shadow root, so your button { } cannot break its toolbar and its styles cannot reach your page. The chrome takes its colours from custom properties you can set from outside.

It speaks nine languages. en, ja, de, es, fr, id, it, ko, pt — the interface and the readability findings, never the document.

It hands back the keyboard. save="host" leaves Cmd/Ctrl+S to the page around it, for an app that saves the figure as part of its own document.

Also available

@figureit/react wraps this in a component with typed props and callbacks. @figureit/iframe runs it in an isolated frame and speaks to it over postMessage.

Documentation

docs.figureit.io/embed — options, events, methods, and the saving contract.

Licence

MIT.