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

praxis-kit

v1.0.2

Published

Praxis Kit — HTML semantics, ARIA requirements, and component composition rules as executable contracts, shared across every framework adapter. The single npm package for all adapters and tooling.

Readme

praxis-kit (packages/kit)

The single published package. Everything users install comes from here; every other workspace in the repo is private and gets bundled into this package's entry points at build time.

pnpm add praxis-kit

Status

Built (tsdown). The public exports surface, the framework-neutral entry files (contract.ts / guards.ts / html.ts / utils.ts — thin re-exports of @praxis-kit/core, primitive, and diagnostics), and Changesets (this is the only package it versions) are all in place. All 7 framework adapters are ready, including Solid and Svelte's declaration file — both formerly deferred gaps, now resolved (see below). Not yet published (private: true) — pending review of the build itself and the release-process wiring (CI release job, private: false flip, first tag), not on any remaining source gap.

| Entry | Bundles | State | | ----------------------------------------- | -------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | praxis-kit/react (+ /react/legacy) | adapters/react | ✅ ready | | praxis-kit/preact | adapters/preact | ✅ ready | | praxis-kit/vue | adapters/vue | ✅ ready | | praxis-kit/solid | adapters/solid | ✅ ready — real Solid JSX transform via unplugin-solid/rolldown | | praxis-kit/svelte | adapters/svelte | ✅ ready — declarations generate correctly as of rolldown-plugin-dts@^0.28.5 (via tsdown 0.23.0) | | praxis-kit/lit | adapters/lit | ✅ ready | | praxis-kit/web | adapters/web | ✅ ready | | praxis-kit/tailwind (+ .css) | lib/tailwind | ✅ ready | | praxis-kit/eslint | plugins/eslint | ✅ ready | | praxis-kit/ts-plugin | plugins/typescript (CJS) | ✅ ready | | praxis-kit/vite-plugin | plugins/vite | ✅ ready — requires the consumer's own typescript at runtime (real import ts from 'typescript', not a build artifact) | | praxis-kit/codemod | tooling/codemod | ✅ ready — fully self-contained; ts-morph vendors its own TypeScript, no peer needed | | praxis-kit/{contract,guards,html,utils} | this folder | ✅ ready |

Formerly-deferred gaps, now resolved

  • Solid. No rolldown-native Solid JSX transform was known to exist in this workspace when this build was first written. unplugin-solid/rolldown (backed by babel-preset-solid, the same compiler esbuild-plugin-solid wraps for ../pk's tsup build) fills that gap — confirmed via tsdown's own documented Solid recipe.
  • Svelte's type declarations. svelte's own shipped types use an ambient declare module 'svelte' { ... } augmentation rather than plain top-level exports, which [email protected] couldn't bundle through. Fixed upstream in rolldown-plugin-dts@^0.28.5 ("treat script-style ambient declarations as modules"), pulled in via a tsdown bump to 0.23.0.

Build

tsdown.config.ts (this folder) — one entry per published subpath, plus a shared _shared/diagnostics chunk. Two invariants scripts/postbuild.ts enforces after the build:

  1. No unpublished names in output. JS bundles internal @praxis-kit/* packages directly (deps.neverBundle opts out only each entry's framework peer and @praxis-kit/diagnostics); declarations resolve @praxis-kit/* sources via dts.compilerOptions.paths. publint checks the packed result (pnpm lint:pkg).
  2. Single Diagnostics identity. @praxis-kit/diagnostics is built once into dist/_shared/diagnostics.* and every other entry's external @praxis-kit/diagnostics specifier is rewritten to a relative import into it — a class with private members bundled per entry would be a different type and a different runtime class in each.

Framework packages (react, vue, preact, solid-js, lit, svelte) stay optional peer dependencies. typescript is an optional peer too, for vite-plugin specifically — codemod needs none (see above), and no other entry touches it.

Verifying a release candidate

publint and a workspace typecheck check dist/ shape and source types — neither installs the published package the way a real consumer would. pnpm --filter praxis-kit test:pack does: builds fresh, packs, installs the tarball plus every framework peer into an isolated fixture (outside this repo's own pnpm workspace, so nothing resolves via hoisting), imports every plain-JS public entry, resolves types for every typed entry, and runs praxis-codemod through its real .bin symlink — the exact sequence that caught two real bugs no amount of publint/typecheck/lint surfaced (see DECISIONS.md). Wired into prepublishOnly, so a real npm publish can't skip it.

See DECISIONS.md ("packages/kit — real build (tsup → tsdown)") for the full writeup, including why this isn't a straight port of ../pk's tsup config.