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

v0.1.1

Published

Shared logic for the @directorkit layer chain — utils, composables and types. A Nuxt layer with no components.

Readme

@directorkit/common

The base of the @directorkit/* layer chain: shared utils, composables and types. No components, no modules, no opinions about UI — every other @directorkit layer extends this one, and an app can extend it directly for the types alone.

Install

npm install @directorkit/common
// nuxt.config.ts
export default defineNuxtConfig({
  extends: ["@directorkit/common"],
});

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

What is in it

Everything below is auto-imported by Nuxt once the layer is extended.

| | | | --- | --- | | useMaybeRef(value) | Normalize a MaybeRef<T> into a real Ref<T> | | utf8ToBase64 / base64ToUtf8 | Base64 that survives non-ASCII (plain btoa does not) | | makeDeepDiff(a, b) | Deep diff of two objects — the primitive behind partial API updates | | isEmail(value) | Email shape check, shared with the forms validators | | hasInjection(key), tryProvide(key, fn) | Provide/inject guards for optional component context | | lerp, toPercentage, getRandomIntBetween | Small math helpers |

Types are importable from #layers/director-common/app/types/*Result<T, E>, Optional<T>, AllowNull<T, Nullable>, DeepPartial<T>, MaybeRef<T, S>, Promiseable<T>, LazyFn<T>, Dictionary<K, V>, KeyValue<K, V>, DayOfWeek, and the component helpers ComponentLoader / EmitsToEvents<T>. Result in particular is the repo-wide convention for fallible operations: { success: true, value } or { success: false, error }.

Documentation

The full architecture — the layer graph, why these ship as layers and not a built library — lives in the repo's ADRs.

License

MIT © Tomáš Petržela