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

@capxul/sdk-react

v1.0.0-alpha.18

Published

The React projection over `@capxul/sdk`. It owns provider lifecycle, TanStack Query bindings, cache invalidation, and React-friendly error state while the Core SDK remains the domain and transport boundary.

Readme

@capxul/sdk-react

The React projection over @capxul/sdk. It owns provider lifecycle, TanStack Query bindings, cache invalidation, and React-friendly error state while the Core SDK remains the domain and transport boundary.

"use client";

import { CapxulProvider } from "@capxul/sdk-react";

export function Providers({ children }: { children: React.ReactNode }) {
  return (
    <CapxulProvider publishableKey={process.env.NEXT_PUBLIC_CAPXUL_PUBLISHABLE_KEY!}>
      {children}
    </CapxulProvider>
  );
}

Public shape

  • CapxulProvider creates or accepts one CapxulClient and owns the React query boundary.
  • useCapxul exposes bootstrap status, failure, and retry.
  • useCapxulOrgLifecycle(orgId) exposes one Organization's durable setup and retry state; Organization data hooks wait for that same scope to be ready.
  • useCapxul* hooks project SDK method bundles into TanStack queries and mutations.
  • The root export also contains selected headless slot components. They are a separate public surface, not a substitute for the hook catalog.

The packed npm package exposes only @capxul/sdk-react. The workspace-only @capxul/sdk-react/headless subpath is not present in publishConfig.exports; consumer examples must import packed symbols from the root.

Documentation

  • Maintainer context — ownership, invariants, proof, and update triggers.
  • Architecture — provider, client, hook, and cache execution paths.
  • Proof map — what package checks prove and what remains a live-system claim.
  • React SDK guide — tutorials, how-to guides, reference, and explanation.
  • Hook catalog — one reference page per public hook.

Development

Run package checks through Vite+:

vp run --filter @capxul/sdk-react check-types
vp run --filter @capxul/sdk-react test
vp pack --filter @capxul/sdk-react