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

@sponsorcoin/spcoin-panels

v0.0.7

Published

Merit Wallet's independent panel-visibility engine (single write chokepoint, no ExchangeContext dependency) — shared between spcoin-nextjs-front-end and the Merit Wallet browser extension (spCoinExtension).

Vulnerabilities

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

Links

Git

Maintainers

sponsorcoinsponsorcoin

Keywords

Readme

@sponsorcoin/spcoin-panels

Merit Wallet's own, independent panel-visibility engine: a plain pub/sub store (meritPanelState), a useSyncExternalStore-based read hook (usePanelVisible), and a gating component (MeritPanelGate) — with a single write chokepoint (setPanelVisible) and zero dependency on spcoin-nextjs-front-end's ExchangeContext. See spcoin-nextjs-front-end/docs/design/extensionPlan.md §7 for the full design/reasoning.

What's actually published here

Only src/ — panelState.ts, usePanelVisible.ts, MeritPanelGate.tsx, index.ts. Those four files are genuinely portable: their only external import is SP_COIN_DISPLAY from @sponsorcoin/spcoin-common/panels (already published), plus react.

node_source/spCoinPanels/AssetSelectDropDowns/ (a sibling of this packages/ folder, one level up) is not part of this package and is not portable yet: every file in it imports directly from the web app's own @/lib/... and @/components/... tree (usePanelTree, PanelGate, useOpenActiveListPanel, useSelectionCommit, and others) — real app-internal dependencies, not something a tsconfig.json/package.json can paper over. Decoupling those the same way this package's own src/ was already decoupled is a separate, much larger effort (on the order of the original panel-extraction work itself, not a rename) — tracked, not attempted here.

Moved into this packages/@sponsorcoin/spcoin-panels/ shape from a flat node_source/spCoinPanels/engine/ (2026-09-10, same day) to match the sibling packages' layout — required by app/api/spCoin/access-manager/route.ts's getPackageWorkspaceRoot(), which hardcodes <workspace root>/packages/..., so this package could be wired into SpCoinAccessController's "NPM Deployment" upload/download/ install panel like spcoin-common/spcoin-lib/spcoin-access-modules already are.

Build

npm run build      # tsc -p tsconfig.json  ->  dist/
npm run typecheck   # tsc --noEmit -p tsconfig.json

Publish

Not yet run from this repo — needs an npm auth token supplied by the package owner. Once available: npm publish --access public from this directory after npm run build.