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

@directorkit/core

v0.1.1

Published

Administration building blocks for Nuxt — app shell, navigation and CRUD scaffolds built on @directorkit/ui.

Downloads

255

Readme

@directorkit/core

Pre-assembled administration building blocks — the app shell and its navigation — built on @directorkit/ui. Extending this layer gives you the component kit as well; apps customize by overriding the layer, not by forking it.

Install

npm install @directorkit/core
// nuxt.config.ts
export default defineNuxtConfig({
  extends: ["@directorkit/core"],
});
// uno.config.ts — required, inherited from @directorkit/ui
export { default } from "@directorkit/ui/uno.config";

@directorkit/core is a Nuxt layer, not a built library: it ships raw source and the consuming app's Vite compiles it. nuxt, vue and vue-router are peer dependencies.

Components

| Component | What it does | | --- | --- | | <DAppShell> | The admin frame: a #left rail, a #header and the default content slot. Layout only | | <DNavigation> | Renders a section → group → item tree; resolves the active entry from the route | | <DNavigationEntry>, <DNavigationEntryBody> | The single entry, split so a consumer can restyle the body without re-implementing the link |

<script setup lang="ts">
import { House, Users } from "@lucide/vue";

const collapsed = ref(false);

// Sections hold groups, groups hold items — each keyed. `icon` is a component,
// not a name: lucide icons are auto-imported, so a string could not be resolved.
const sections: Array<DNavigationSection> = [
  { key: "main", groups: [{ key: "overview", items: [{ label: "Dashboard", to: "/", icon: House }] }] },
  { key: "manage", groups: [{ key: "people", label: "Manage", items: [{ label: "Users", to: "/users", icon: Users, badge: "12" }] }] },
];
</script>

<template>
  <DAppShell :collapsed="collapsed">
    <template #left>
      <DNavigation :sections="sections" :collapsed="collapsed" tooltip />
    </template>
    <template #header>
      <!-- your page header -->
    </template>
    <NuxtPage />
  </DAppShell>
</template>

Items nest (children), gate themselves out of the tree (skipIf), and carry badges or chips. Passing collapsed narrows the rail to icons, with labels becoming tooltips and children becoming flyouts. For a single unlabelled group, :items is shorthand for the full :sections tree.

useNavigation(sections) is the composable behind the component — the active item is resolved once, centrally, rather than each entry deciding for itself (ADR-0016); useNavigationActive() reads that result. useIsDirector() / useProvideIsDirector() let a component tell whether it is rendering inside the shell.

Documentation

See the repo's ADRs, in particular 0016 (AppShell is layout only).

License

MIT © Tomáš Petržela