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

@zedtech/zedkit-quality

v1.1.1

Published

Shared quality setup: UI lint preset, route/view/data layer boundaries, one strict TypeScript base, and repo hygiene bins — consume, do not copy.

Readme

@zedtech/zedkit-quality

npm version license: MIT

Shared quality setup: UI lint preset, route/view/data layer boundaries, one strict TypeScript base, and repo hygiene bins. Consume it from any repo — do not copy it. Original work by the same author.

Install

pnpm add -D @zedtech/zedkit-quality

Peer dependencies (eslint, eslint-plugin-jsx-a11y, eslint-plugin-better-tailwindcss, typescript-eslint) install alongside it.

Usage

// eslint.config.mjs
import { defineLayers, uiPreset } from "@zedtech/zedkit-quality";

export default [
  ...uiPreset({ entryPoint: "./app/globals.css" }),
  ...defineLayers({
    kitPackage: "@acme/ui",
    viewDirs: ["app/**/ui/**"],
    dataDirs: ["lib/**"],
    actionPatterns: ["@/lib/*", "**/actions", "**/actions/**"],
  }),
];
// tsconfig.json
{
  "extends": "@zedtech/zedkit-quality/tsconfig",
  "compilerOptions": { "outDir": "dist", "rootDir": "src" },
  "include": ["src"]
}
// package.json — hygiene bins (optional extra --dirs/--files/--allow)
{
  "scripts": {
    "dev": "zedkit-sync-env && next dev",
    "check": "zedkit-check-no-artifacts && zedkit-check-no-secrets"
  }
}

When to use

Reach for this package when several repos must enforce the same gates: UI lint rules, layer boundaries, one strict tsconfig base, and the same artifact / secret / .env hygiene. One import (or bin) per need, versioned updates everywhere. For AI agent setup (skills, subagents, commands) see @zedtech/zedkit-ai instead.

API

  • nodePreset({ tryCatchSource? }) — flat-config blocks for Node/TS packages: eslint + typescript-eslint recommended, raw try/catch ban, deep relative import ban. Default message points at @zedtech/zedkit-core; override tryCatchSource when the consumer re-exports the helpers under another name.
  • uiPreset({ entryPoint }) — flat-config blocks for .tsx/.jsx: jsx-a11y recommended, Tailwind hygiene, tokens-only classes (no) w-[13px] / gap-[0.75rem]; Radix w-[var(--radix-*)] stays; no focus:ring-2 / focus-visible:ring-2 — use focus-ring), no style attributes, no forwardRef (ref is a prop; see packages/ui/src/button.tsx), no explicit any, files ≤ 300 lines and functions ≤ 60, no raw try/catch. entryPoint (your Tailwind CSS entry) is required: it is the one thing that varies per repo.
  • defineLayers({ kitPackage, viewDirs, dataDirs, actionPatterns, extraPatterns }) — no-restricted-imports blocks for routes -> views -> data: the UI kit is only imported from views, views never import data clients or actions, data files import no UI. extraPatterns (optional, { kitScope?, viewData?, dataUi? }) merges your own bans into each block — use it instead of a second no-restricted-imports block, which would replace these per flat-config key semantics.
  • defineLayers({ preset: "feature-folders", kitPackage, featureRoot }) — same helper, feature-folder mapping: UI imports ports (not adapters), adapters are injected at the composition root, model is pure. Bans apply only under featureRoot. Live example: apps/docs/features/note-list (running at /examples/note-list).
  • @zedtech/zedkit-quality/tsconfig — the strict base (strict, exactOptionalPropertyTypes, noUncheckedIndexedAccess, noUnusedLocals, and more). Extend it, do not copy it.
  • zedkit-sync-env [root] — copy .env.example to .env when missing; otherwise append keys the example gained. Existing values stay.
  • zedkit-check-no-artifacts — fail if tracked files match the default artifact list (build/cache dirs, *.tsbuildinfo, Playwright reports…), match .gitignore (uses --no-index so ignored-but-tracked files are caught), or exceed 200KB. --dirs / --files / --allow (repeatable) append to the defaults; --max-bytes changes the cap.
  • zedkit-check-no-secrets — fail if a tracked .env other than .env.example or a high-signal token/key pattern is in git.

Find helpers by need in CATALOG.md.

Install or copy?

Install it: these configs must stay identical across repos, and a copy drifts silently. Versioned updates propagate through normal bump PRs.

Verify

pnpm --filter @zedtech/zedkit-quality typecheck && pnpm --filter @zedtech/zedkit-quality lint && pnpm --filter @zedtech/zedkit-quality test