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

@glixo/extension-sdk

v0.1.0

Published

Typed guest-side helpers for Glixo WebAssembly extensions

Readme

TypeScript guest SDK

The @glixo/extension-sdk source package contains broker, state, logging, workspace, guest-envelope, and LLM event helpers. NdjsonStream operates on WIT broker bytes, keeps response lines bounded, and does not call fetch or Node networking APIs. Adapters must implement the interfaces with generated Jco imports.

The npm package is source-only in this checkout and has not been published. CLI-generated projects vendor this folder at vendor/glixo-extension-sdk until a public npm release is qualified.

Jco result errors

Jco maps a top-level WIT result<T, string> import to T on success and throws on the err arm; an option<T> is T | undefined. WIT variants keep their kebab-case tags (for example, { tag: "tool-call-details", val: details }). Do not model these as { tag: "ok", val }, { tag: "err", val }, or { tag: "none" }.

Use captureWitResult(() => generatedImport(...)) to adapt a generated import to the SDK's internal Result<T> type. At an exported function whose WIT signature returns result<T, string>, catch internal errors and call throwWitError(error); throwing an Error object traps instead of returning the WIT error arm. The helper bounds error payloads to 256 characters.