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/ssr

v0.1.0

Published

Server-side rendering helpers for Vitibase — cookie-based sessions for Next.js, Remix, SvelteKit and other frameworks that render on the server.

Readme

@vitibase/ssr

Server-side rendering helpers for Vitibase — cookie-based auth sessions for Next.js, Remix, SvelteKit and anything else that renders on a server.

npm install @vitibase/client @vitibase/ssr
// utils/vitibase/server.ts
import { createServerClient } from '@vitibase/ssr'
import { cookies } from 'next/headers'

export const createClient = (cookieStore: Awaited<ReturnType<typeof cookies>>) =>
  createServerClient(
    process.env.NEXT_PUBLIC_VITIBASE_PROJECT_REF!,
    process.env.NEXT_PUBLIC_VITIBASE_ANON_KEY!,
    {
      cookies: {
        getAll: () => cookieStore.getAll(),
        setAll: (list) =>
          list.forEach(({ name, value, options }) => cookieStore.set(name, value, options)),
      },
    }
  )

createServerClient and createBrowserClient take a project ref or a full URL, exactly like @vitibase/client. Everything else — parseCookieHeader, serializeCookieHeader, the chunking helpers, the cookie option defaults — is re-exported unchanged.

What this package is

A thin layer over @supabase/ssr, which does the genuinely hard part: keeping one auth session consistent across a server render, a client hydration and a middleware refresh, for frameworks that each disagree about how cookies are read and written. Reimplementing that would be a way to introduce session bugs, not a way to own the code.

Licence and attribution

Apache-2.0. Depends on @supabase/ssr, which is Apache-2.0 licensed and copyright Supabase, Inc. Supabase is a trademark of Supabase, Inc., which does not endorse Vitibase.