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

noodle-embed

v0.1.0

Published

Embed a nanoodle workflow, rendered read-only, in any page — one ES module, zero dependencies, decodes the share link locally.

Readme

noodle-embed

Embed a nanoodle workflow in any page. One ES module, zero dependencies. Drop a share link into a <noodle-embed> tag and readers see the workflow — nodes, wires, labels — rendered read-only right in your post, with an Open in nanoodle → button that loads the real thing on their canvas, ready to run or remix.

<script type="module" src="noodle-embed.mjs"></script>
<noodle-embed src="https://nanoodle.com/#g=H4sIAAAA..."></noodle-embed>

That's the whole integration.

Why this exists

A nanoodle share link carries the entire workflow inside the URL fragment — nothing is uploaded, nothing is hosted. That's great for privacy and terrible for previews: pasted into a blog post, the link is just a wall of base64. noodle-embed decodes that fragment locally in the reader's browser (no fetch, no analytics, nothing leaves the page — the same promise nanoodle itself makes) and draws the graph, so the workflow is visible where your readers already are.

Usage

<script type="module" src="noodle-embed.mjs"></script>

<!-- a workflow link (#g= / #j=) or an app link (#a=) -->
<noodle-embed src="https://nanoodle.com/#g=..."></noodle-embed>

<!-- taller canvas for stacked graphs (default 340, clamped 160–1200) -->
<noodle-embed src="https://nanoodle.com/play#a=..." height="480"></noodle-embed>

Attributes:

| attribute | what it does | |---|---| | src | A nanoodle share URL, or a bare #g=... fragment. All four fragment tags are understood: #g= (gzip graph), #j= (plain graph), #a= (gzip app), #a=u (plain app). App embeds show the app's name. | | height | Canvas height in px. Default 340, clamped to 160–1200. |

Behavior worth knowing:

  • Read-only viewer. Field contents (prompts, uploads) are never shown — only structure: node cards with their type emoji/label (or custom name) and the wires between them. Running happens one click away, in nanoodle.
  • Graceful fallback. An undecodable src still renders the frame and the Open-in-nanoodle button — a broken preview never becomes a dead end.
  • Full share URLs only. link.nanoodle.com short links can't be decoded without a network round-trip, so embed the full-length link (the graph is in the fragment). The share popover's copy button gives you exactly that.
  • Self-contained. No external requests of any kind, so it works under strict CSPs (default-src 'self') and in offline docs.

Development

npm test          # node --test — decode, layout, fallback logic (Node ≥ 20)
open demo.html    # serve the folder and eyeball the element

The pure helpers (decodeShareUrl, layoutGraph, openUrl, TYPE_META) are exported for reuse and tests; the custom element registers itself only in browsers.

Roadmap

  • Live run inside the embed via nanoodle-js (nanoodle/browser), bring-your-own-key — the engine already runs in browsers; the embed just needs a key affordance that meets the privacy bar.
  • npm publish + CDN copy-paste snippet.

License

MIT — see LICENSE. Not affiliated with NanoGPT. Build workflows at nanoodle.com.