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

@lyku/para-check

v0.0.1-pre.1

Published

Batch type-checker for `.pui` Para UI components (svelte-check for the Para substrate). Projects every `.pui`/`.svelte` in a workspace to typed TSX via the same lowering + svelte2tsx pipeline the parabun LSP uses, type-checks the projections in one TypeSc

Readme

@lyku/para-check

Batch type-checker for .pui Para UI components — svelte-check for the Para substrate. One command, tsc-style output, non-zero exit on errors:

pui-check --workspace apps/webui
# src/routes/+page.pui(8543,97): error TS2339: Property 'revokeApiToken' does not exist …
# pui-check: 296 errors in 8 of 30 components

Why svelte-check can't do this

svelte-check hardcodes the .svelte extension for its svelte2tsx projection, so it silently skips every .pui — and its bundled language service is inert against the @lyku/para-ui fork (verified: planted errors in both .pui and shadow .svelte files go uncaught while it reports 0 errors). A green svelte-check run over a Para codebase is vacuous.

How it works

Reuses the exact pipeline the parabun LSP trusts for in-editor .pui intelligence (editors/lsp/pui-transform.ts, bundled in):

  1. Para lowering (signal / derived / effect / prop → Svelte 5 runes) over a MagicString, producing a real sourcemap.
  2. svelte2tsx over the lowered source, producing typed TSX and a second map.
  3. One ts.Program over the workspace tsconfig's own ambient roots (extends resolved, so SvelteKit's $app/$lib paths, app.d.ts, generated $types all participate), the svelte2tsx shims (inlined — the target workspace does not need svelte2tsx installed), and every projection. import X from "./X.pui" resolves to the virtual X.pui.tsx, so component prop types are real across files.
  4. Diagnostics for the projections only (plain .ts is tsc's job), mapped back through the chained sourcemaps to original .pui positions.

TypeScript itself is resolved from the target workspace at runtime — the diagnostics come from the compiler the project actually builds with.

Flags

| Flag | Meaning | | --- | --- | | --workspace <dir> / -w | project root to check (default: cwd) | | --tsconfig <file> | explicit tsconfig (default: nearest to workspace) | | --verbose | list projected components on stderr |

Template expressions are checked, not just scripts; a component the projector cannot parse fails the check (reported on that file) instead of crashing it.

Pre-release: API may change before 0.1.0.