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

@superdb/client

v0.1.0

Published

Drop-in compat layer for @supabase/supabase-js — points at SuperDB instead

Readme

@superdb/client

Drop-in replacement para @supabase/supabase-js — aponta para o SuperDB ao invés de Supabase Cloud.

Por que existir?

Aceleração de migração. Trocando 1 import:

- import { createClient } from '@supabase/supabase-js';
+ import { createClient } from '@superdb/client';

…seu código de auth funciona idêntico, agora apontando para SuperDB.

O que esta implementado (Sprint 2)

  • client.auth.signUp
  • client.auth.signInWithPassword
  • client.auth.signInWithOtp (email)
  • client.auth.verifyOtp
  • client.auth.signInWithOAuth (google/github/apple)
  • client.auth.signOut
  • client.auth.getSession / getUser / refreshSession
  • client.auth.mfa.enroll / verify / factors

Dados — implementado

  • client.from(table) — query builder PostgREST real (select/insert/update/delete + eq/neq/gt/gte/lt/lte/like/ilike/is/in, order/limit/range/single, thenable). Fala com o data-plane (https://api.superdb.com.br, SEM /rest/v1), mandando o data_plane_token ES256 da sessão + Accept-Profile: proj_<slug>. Exige project: '<slug>' no createClient.
  • client.rpc(fn, args)POST /rpc/<fn> no data-plane.

Ainda stub (jogam erro com mensagem clara)

  • client.storage.from(bucket) — use @supabase/storage-js apontando para https://storage.superdb.com.br.
  • client.channel(name) — use @supabase/realtime-js apontando para https://realtime.superdb.com.br.

Install

bun add @superdb/client
# ou npm/pnpm/yarn

Quickstart

import { createClient } from '@superdb/client';

const supabase = createClient('https://acme.superdb.com.br', 'anon-key', {
  project: 'acme', // X-SuperDB-Project header
});

const { data, error } = await supabase.auth.signInWithPassword({
  email: '[email protected]',
  password: 'senha-forte',
});

const { data: { session } } = await supabase.auth.getSession();

Compat shape

Pra que codigo que usa import type { SupabaseClient } from '@supabase/supabase-js' ainda compile, exportamos os mesmos tipos com nomes alinhados:

import type { SupabaseClient, Session, User, AuthError } from '@superdb/client';

User é o SuperDBUser reexportado.

License

MIT — (c) 2026 SuperDB