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

@umnburrow/core

v0.2.2

Published

Shared Burrow component, API and model library.

Readme

@umnburrow/core

Shared code for the three Burrow clients — the web app (frontend/web), the mobile app (frontend/app) and the admin panel (frontend/admin).

The package has two entry points.

@umnburrow/core

The React component library: Button, Card, Modal, Input, Paginator and friends. Web only — it depends on react-aria-components and lucide-react.

import { Button, Card } from "@umnburrow/core"
import "@umnburrow/core/style.css"

@umnburrow/core/api

Every call the clients make to the backend, the models those calls return, and the formatting helpers shared between them. This entry point touches no React, no DOM and no React Native, so the mobile app consumes it too.

Configure it once at startup, before anything renders:

import { configureApi } from "@umnburrow/core/api"

configureApi({
    baseUrl: import.meta.env.VITE_BASE_URL,
    cdnUrl: import.meta.env.VITE_CDN_URL,
    getToken: () => store.get(authToken),
    getRefreshToken: () => store.get(refreshTokenAtom),
    setToken: (token) => store.set(authToken, token),
    setRefreshToken: (token) => store.set(refreshTokenAtom, token)
})

Each client keeps its own session storage — cookies on web, AsyncStorage on mobile, localStorage on admin — and hands the API layer the accessors. The client attaches the bearer token, refreshes it once on a 401 and retries the original request.

Then call the endpoints directly; the token is never passed by hand:

import { getBurrow, joinBurrow, type BurrowResponse } from "@umnburrow/core/api"

const response: BurrowResponse = await getBurrow(id)
await joinBurrow(id)

The models mirror the Kotlin models in backend/src/main/kotlin. When a route or a payload changes on the backend, change it here — not in the clients.

Development

bun run build   # type check, bundle both entries, emit .d.ts
bun run dev     # rebuild on change
./bump_publish.sh

The clients depend on a published version, so a change here has to be published before they can pick it up.