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

@pluxel/market

v0.1.0

Published

Developer toolkit for the Pluxel marketplace ecosystem. The package bundles two things:

Downloads

40

Readme

@pluxel/market

Developer toolkit for the Pluxel marketplace ecosystem. The package bundles two things:

  1. GitHub Actions under actions/ for publishing plugins and validating manifests.
  2. Hono RPC helpers under src/ so dashboards or CLIs can talk to the worker with end-to-end typing.

RPC client

import { createMarketRpcClient } from "@pluxel/market";

const client = createMarketRpcClient({
  baseUrl: "https://worker.example.com",
  headers: async () => ({
    Authorization: `Bearer ${await getToken()}`,
  }),
});

// Health check
await client.health();

// Get the latest snapshot (flat package list + tags)
const snapshot = await client.snapshots.current();

// Get summary statistics (version, counts)
const stats = await client.snapshots.stats();

// Publish a package
await client.webhook.submit(
  { packageName: "pluxel-plugin-example", version: "1.0.0" },
  githubOidcToken
);

createMarketRpcClient accepts either a base URL string (legacy signature) or a full options object with:

  • headers / init / fetch hooks for SSR, custom auth, or alternative runtimes
  • routes overrides when the worker is reverse-proxied
  • .request(path, init) escape hatch for custom endpoints

renderSnapshotDashboard still mounts the full React dashboard, but it now accepts a snapshotSource option so you can hydrate from any loader (REST, GraphQL, gRPC) without pulling in the RPC client. Pass client or snapshotSource, plus the existing knobs:

  • appearance ("light"/"dark")
  • cached embeds via initialSnapshot + hydrateOnInit={false}
  • resolveMetadata + tagDictionary for repo URLs, tag IDs, highlights, version history, etc.
  • enableInstallQueue + onInstallSubmit to surface batch install
  • namePrefixesToTrim (e.g. ["pluxel-plugin-"]) to hide redundant prefixes

Both the component and the renderer share the same props (DashboardOptions / SnapshotDashboardProps), so they can be reused in your own React tree without touching the DOM helper.

Building

bun run --filter @pluxel/market build