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

@voyant-travel/admin-app

v0.61.0

Published

First-party admin app composition package.

Readme

@voyant-travel/admin-app

First-party admin app composition package.

The reusable shell implementation lives in @voyant-travel/admin/app/* so the top-level admin package owns the packaged staff shell and extension surface. This package re-exports those shell helpers for compatibility and owns the domain-backed core extension bundle that imports first-party domain React packages.

What it provides

  • createAdminRouter({ routeTree }) / createAdminQueryClient() — TanStack Router + QueryClient with the Voyant defaults: intent preloading with matched staleTime, scroll restoration, default not-found page, and QueryClient SSR dehydrate/hydrate.
  • adminRootHead({ title, ... }) / AdminRootShell / AdminRootErrorBoundary — the root route internals, including the pre-hydration theme/locale bootstrap script (no theme flash) and an error boundary that survives outside the provider tree.
  • createAdminWorkspaceBeforeLoad({ getCurrentUser }) — the auth guard, in beforeLoad so the redirect short-circuits child loaders instead of racing them.
  • AdminWorkspaceShell — bootstrap gate → per-user message overrides → locale sync → workspace layout, with AdminRouterLink (Slot-compatible, external-URL-aware) as the default nav link. Pass destinations (a satisfies AdminDestinationResolvers map) to mount the semantic-destination contract: packaged pages resolve AdminDestinations keys to hrefs via useAdminHref/useAdminNavigate, and the shell routes them through the app router.
  • createAdminCoreExtension(options?) — dashboard, account, and settings route contributions backed by first-party domain React packages.

Usage

// src/router.tsx
import { createAdminRouter } from "@voyant-travel/admin/app"

export const getRouter = () => createAdminRouter({ routeTree })

// src/routes/__root.tsx
import { AdminRootErrorBoundary, AdminRootShell, adminRootHead } from "@voyant-travel/admin/app/root"

export const Route = createRootRouteWithContext<AdminRouterContext>()({
  head: () => adminRootHead({ title: "Acme Admin" }),
  shellComponent: AdminRootShell,
  component: RootComponent, // app-owned: mounts the app's provider stack
  errorComponent: AdminRootErrorBoundary,
})

// src/routes/_workspace/route.tsx
import {
  AdminWorkspacePendingFallback,
  AdminWorkspaceShell,
  createAdminWorkspaceBeforeLoad,
} from "@voyant-travel/admin/app/workspace"

export const Route = createFileRoute("/_workspace")({
  ssr: "data-only",
  beforeLoad: createAdminWorkspaceBeforeLoad({ getCurrentUser }),
  loader: ({ context }) => ({ user: context.user }),
  pendingComponent: AdminWorkspacePendingFallback,
  component: () => (
    <AdminWorkspaceShell
      user={user}
      icons={navigationIcons}
      extensions={(messages) => createMyAdminExtensions(messages)}
      destinations={myAdminDestinations} // key → href resolvers, satisfies AdminDestinationResolvers
      onSignOut={() => signOut({ redirectTo: "/sign-in" })}
    >
      <Outlet />
    </AdminWorkspaceShell>
  ),
})

What stays app-owned: the provider list (which domain modules are mounted), extension definitions, navigation icons, branding, and the auth client.

New first-party code should import shell helpers from @voyant-travel/admin/app/* and the domain-backed core extension from @voyant-travel/admin-app/core-extension.

License

Apache-2.0