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

@myatthirikhin/chat-supabase

v0.1.0

Published

Supabase chat backend for @myatthirikhin/chat-core — Postgres schema, RLS, Realtime and Storage included.

Readme

@myatthirikhin/chat-supabase

A chat backend on Postgres, RLS, Realtime and Storage — the adapter and the schema.

pnpm add @myatthirikhin/chat-core @myatthirikhin/chat-supabase @supabase/supabase-js

Then apply the SQL. → SETUP.md — installing the package is half the job; the other half is a database.

import { ChatClient } from '@myatthirikhin/chat-core';
import { createSupabaseChatProvider } from '@myatthirikhin/chat-supabase';

const chat = new ChatClient({ provider: createSupabaseChatProvider(supabase) });
await chat.connect({ id: userId, name: 'Ana' });

No tokenProvider: the Supabase session already in your client is the credential. There is no token endpoint to deploy and no secret to rotate — the main practical difference from Stream and Sendbird.

What ships here

| | | |---|---| | src/ | the IMessagingProvider implementation | | sql/ | three migrations: schema + RLS + RPCs, Realtime, Storage | | functions/push-fanout/ | an Edge Function that pushes through Expo's service |

Design notes

  • Keyset pagination on (conversation_id, id desc) — never OFFSET, which is O(offset) and wrong under the concurrent inserts chat has by definition.
  • Read state is a monotonic watermark, not a receipts table. Receipts cost messages × members rows to buy a per-message timestamp no chat UI displays.
  • Soft delete only. A real DELETE emits a Realtime event whose old-record payload is not RLS-filtered — a security decision, not a style one.
  • Three Realtime channels per client, forever, regardless of conversation count. Realtime caps channels at 100 per connection, so one subscription per conversation breaks at 100 conversations.
  • One SECURITY DEFINER helper breaks the members↔messages RLS recursion (42P17).

Scaling

The first wall is concurrent connections (500 on Pro with the spend cap on), not throughput. Then messages/sec, which counts after fan-out. postgres_changes doesn't get faster on a bigger instance; past ~3,000 concurrent subscribers, switch to broadcast-from-database — the SQL is at the bottom of sql/0002_chat_realtime.sql.

License

MIT