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

@vitibase/client

v0.2.0

Published

JavaScript client for Vitibase — Postgres hosted in India, with an instant REST API, auth, storage and realtime.

Readme

@vitibase/client

The JavaScript client for Vitibase — Postgres hosted in India, with an instant REST API, authentication, file storage and realtime.

npm install @vitibase/client
import { createClient } from '@vitibase/client'

const db = createClient(process.env.VITIBASE_PROJECT_REF!, process.env.VITIBASE_ANON_KEY!)

const { data } = await db.from('orders').select('id, total, created_at').eq('status', 'paid')

A project ref, or a URL

createClient takes either. A ref is the twenty-letter identifier on your project's Connect panel, and the URL is built for you:

createClient('abcdefghijklmnopqrst', anonKey) // https://abcdefghijklmnopqrst.vitibase.in
createClient('https://db.example.com', anonKey) // used exactly as given

projectUrl(ref) is exported separately, for the places that need the address rather than a client — a plain fetch against the REST endpoint, a storage URL in an <img>, a health check in a deploy script.

What this package is

A thin layer over @supabase/supabase-js, which it re-exports in full. Vitibase serves the same data-plane API, so writing a second client would mean maintaining a worse one and owning every bug in it. Two things are added: a project ref becomes a URL, and an application's source does not have to name another vendor for a database that is not theirs.

An existing codebase changes one import line and nothing else:

-import { createClient } from '@supabase/supabase-js'
-const db = createClient(process.env.SUPABASE_URL, process.env.SUPABASE_ANON_KEY)
+import { createClient } from '@vitibase/client'
+const db = createClient(process.env.VITIBASE_PROJECT_REF, process.env.VITIBASE_ANON_KEY)

Every other export — the auth and storage types, the realtime constants — is the upstream one, unchanged. The client class is exported as VitibaseClient as well as under its original name; they are the same class, so instanceof and type annotations agree whichever you write.

import type { VitibaseClient } from '@vitibase/client'

function seed(db: VitibaseClient) {
  /* … */
}

ES modules

This package ships ESM only. Node 22 and every current bundler handle that; on older CommonJS setups, await import('@vitibase/client') works.

Licence and attribution

Apache-2.0. It depends on @supabase/supabase-js, which is Apache-2.0 licensed and copyright Supabase, Inc. Postgres is a registered trademark of the PostgreSQL Community Association of Canada. Supabase is a trademark of Supabase, Inc., which does not endorse Vitibase.