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

@juicerq/check

v0.4.0

Published

Lint rules, shared config, and check runner for juicerq's code standard

Readme

@juicerq/check

One command that runs the whole gate: lint, types, and dead code.

juicerq-check runs three tools in order and prints a single summary. It exits non-zero if any of them fails.

| Step | Tool | What it does | | --- | --- | --- | | oxlint | oxlint | Lints with the shared config, type-aware, and applies --fix | | typecheck | your project's script | Runs bun run typecheck — the project's own TypeScript | | knip | knip | Finds unused files, exports, and dependencies |

When --fix rewrites files, the summary names them, so a fix never lands unnoticed.

Install

bun add -d @juicerq/check

Setup

Three pieces.

1. Extend the shared lint config. Create .oxlintrc.json in the project root:

{
	"extends": ["./node_modules/@juicerq/check/.oxlintrc.json"]
}

Add project rules next to extends — they win over the shared ones.

2. Add the scripts. In package.json:

{
	"scripts": {
		"check": "juicerq-check",
		"typecheck": "tsc --noEmit"
	}
}

3. Run it.

bun run check

Requirements

juicerq-check stops with a message when one of these is missing:

  • A typecheck script. It does not bring its own TypeScript setup, it calls yours.
  • typescript installed in the project. Type-aware linting cannot be skipped.
  • A readable package.json in the directory you run from.

Knip reads the project's own knip.json when there is one, and its defaults otherwise.

Rules

Beyond the oxlint correctness set, the shared config caps cyclomatic complexity at 15 (eslint/complexity). The count charges ?. and ?? a branch each, which typescript/prefer-optional-chain (also on in this config) pushes code toward, so the ceiling stays above what ordinary branching reaches.

Read a hit as a pointer to open the file, not as a number to bring down. The count cannot tell a good extraction from a bad one, and a rewrite that scores lower is not automatically the better one.

It also turns on three rules from this package:

  • juicerq/no-conditional-let — an empty let filled by a following if, switch, or ternary. Docs
  • juicerq/no-ternary-return — a return whose whole argument is a ternary. Docs
  • juicerq/no-trivial-call-wrapper — a function whose body is one call forwarding its own parameters. Docs

Exports

  • @juicerq/check/oxlintrc — the shared config, if you would rather import it than reference the path.
  • @juicerq/check/plugin — the oxlint plugin holding the three rules.

License

MIT