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

@bunvex/nextjs

v0.1.0-alpha.1

Published

Next.js and server rendering: fetchQuery, fetchMutation, fetchAction and preloadQuery.

Readme

@bunvex/nextjs

Next.js and server rendering (STUDY-46), the counterpart of Convex's convex/nextjs. Every function reads the deployment URL from NEXT_PUBLIC_BUNVEX_URL (which bunvex dev writes to .env.local) unless url is given, and its requests are never cached by Next.js (cache: "no-store").

Load data in a Server Component, Server Action or Route Handler:

import { anyApi as api } from "@bunvex/client";
import { fetchMutation, fetchQuery } from "@bunvex/nextjs";

const messages = await fetchQuery(api.messages.list, {}, { token }); // `token`: the user's JWT, if any
await fetchMutation(api.messages.send, { body: "hi" });

Or preload a query on the server and keep it live on the client:

// Server Component
import { preloadQuery } from "@bunvex/nextjs";

export async function Page() {
  const preloaded = await preloadQuery(api.messages.list);
  return <Messages preloaded={preloaded} />;
}

// Client Component ("use client"), under BunvexProvider
import { type Preloaded, usePreloadedQuery } from "@bunvex/react";

export function Messages(props: { preloaded: Preloaded<typeof api.messages.list> }) {
  const messages = usePreloadedQuery(props.preloaded); // the server's value first, then live
  return <ul>{messages.map((m) => <li key={m}>{m}</li>)}</ul>;
}

Options: token, url, skipDeploymentUrlCheck.