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

@qlover/next-kit

v1.1.0

Published

Shared Next.js app shell: isomorphic common layer, server runtime, and client runtime

Readme

@qlover/next-kit

Shared Next.js app shell extracted from examples/next-seed / examples/next-oauth.

One package, three runtime entries — so Node-only and client-only code never get mixed by accident.

Entries

| Import | Runtime | May use | |--------|---------|---------| | @qlover/next-kit / @qlover/next-kit/common | isomorphic | types, schemas, pure helpers | | @qlover/next-kit/server | Node / Next route handlers | next/server, cookies, Node APIs | | @qlover/next-kit/client | Client ("use client") | React hooks, DOM, sonner toasts |

import { /* ... */ } from '@qlover/next-kit/common';
import { /* ... */ } from '@qlover/next-kit/server';
import { /* ... */ } from '@qlover/next-kit/client';

Dependency rules

common  ──► (nothing in this package)
server  ──► common
client  ──► common

server  ✕── client
client  ✕── server

Root export (.) is common only. Always import /server or /client explicitly when you need those runtimes.

Peer side effects (app responsibility)

This package does not import reflect-metadata, and does not re-export inject / injectable — apps choose their IOC decorators (e.g. @qlover/corekit-bridge/ioc or inversify). If you use {@link InversifyContainer} or decorators, import the polyfill once at your app entry:

import 'reflect-metadata';

InversifyContainer will throw a clear error if the polyfill is missing. Keeping the side-effect out of the kit avoids pulling it into unrelated client bundles.

Shared validator messages use the next_kit: key namespace (e.g. next_kit:v_email_invalid) so they do not collide with app-local common:v:* keys. Apps own the locale strings for these identifiers.

Why one package (not three)

Same approach as @qlover/oauth-wrapper (server / core / client):

  • One version bump when a shell bug fix touches types + server + client
  • Apps depend on a single package
  • Environment isolation is enforced by entry points + directory rules, not by splitting publish units

Status

0.0.1common, server, and client (services + shell UI: Loading/With/Button/Modal/DialogUIHost/LocaleLink/ClientRenderProvider/UserAuthFailed, hooks, theme init script). Example rewires come next.

Develop

pnpm --filter @qlover/next-kit build
pnpm --filter @qlover/next-kit test
pnpm --filter @qlover/next-kit type-check