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

@pyqdeck/community-sdk

v0.3.0

Published

Typed client for the PYQDeck Community API (posts, comments, members, short links). No Clerk, React or cache inside: the app supplies the token and owns caching.

Readme

@pyqdeck/community-sdk

Typed client for the PYQDeck Community API. It works in React Native (Expo, Hermes) and the browser. It has no cache, no Clerk and no React inside: your app passes a getToken() function and owns caching, retries and optimistic updates (for example with TanStack Query).

import { createCommunityClient, communityKeys } from "@pyqdeck/community-sdk";

const community = createCommunityClient({
  baseUrl: "https://community-api.pyqdeck.in",
  community: "beu", // one client per community
  getToken: async () => (await clerk.session?.getToken()) ?? null,
});

// Read
const feed = await community.posts.feed({ hashtag: "dsa", limit: 20 }); // { items, nextCursor, hasMore }
const next = await community.posts.feed({ cursor: feed.nextCursor! });

// Publish with images in one call (upload, check, create), with progress and cancel
const post = await community.publishPost({
  body: "Dijkstra notes #dsa",
  images: [{ uri, mimeType: "image/jpeg", size }],
  onProgress: (p) => setProgress(p), // 0..1
  signal: controller.signal,
});

// React with TanStack Query: keys always start with the community
useQuery({
  queryKey: communityKeys.feed("beu", { hashtag: "dsa" }),
  queryFn: ({ signal }) => community.posts.feed({ hashtag: "dsa" }, { signal }),
});

Errors

Every failure is a CommunityApiError with status (0 means no answer from the server), a stable code (not_found, unauthorized, too_many_requests, unprocessable_entity, network_error, timeout, aborted), retryAfterMs for rate limits, and requestId to quote in bug reports. message is safe to show to students.

Good to know

  • Every method takes { signal } as its last argument.
  • Responses contain only JSON-safe values (dates are ISO strings), so they can be persisted.
  • Send an idempotency key (publishPost does this for you) so a retry after a timeout never creates a duplicate.
  • The API surface lives at /api/v1. A breaking API change means a new major version of this package.

License

MIT