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

@yuu1111/knip-config

v2.1.0

Published

Shared Knip configuration

Readme

日本語

@yuu1111/knip-config

Shared Knip configuration.

Install

bun add -D @yuu1111/knip-config knip

Usage

Knip loads knip.ts, so import the preset that matches the project and add the entries it cannot infer:

import { application } from "@yuu1111/knip-config/application"

export default {
	...application,
	entry: ["src/main.ts"]
}

Presets

| Preset | includeEntryExports | Use case | |--------|----------------------|----------| | base | — | Shared defaults | | application | false | Applications whose entry points a framework resolves | | library | true | Libraries whose entry points are their public API |

base

Every preset extends base.

| Setting | Value | |---------|-------| | entry | ["quality.json"] | | ignoreExportsUsedInFile | true | | treatConfigHintsAsErrors | true | | treatTagHintsAsErrors | true |

quality-check loads quality.json at run time, so the file counts as an entry point and is not reported as unused. ignoreExportsUsedInFile keeps its exports out of the report, because the public API of a consuming project is the API of quality-check and not the exports of this file. treatConfigHintsAsErrors fails the run when a configuration no longer matches the project. treatTagHintsAsErrors fails the run when a suppression tag no longer suppresses anything.

application

Sets includeEntryExports: false, because the entry points of an application are not a public contract.

library

Sets includeEntryExports: true, so an export that is no longer part of the public API is reported.

Config

A shared preset cannot see dynamic entry points, CLI binaries, or generated files, so the project adds them.

entry is replaced when the project writes its own, so list quality.json too:

export default {
	...application,
	entry: ["src/main.ts", "quality.json"]
}

workspaces does not inherit the top-level entry in the root workspace, so move entry there:

import { application } from "@yuu1111/knip-config/application"

const { entry, ...base } = application

export default {
	...base,
	workspaces: {
		".": { entry },
		"packages/app": { entry: ["src/cli.ts"] }
	}
}

Knip prints a configuration hint when a repository with workspaces also writes entry at the top level, and base fails the run on a hint.

A repository that also holds another project keeps it out of the report with ignore, so its files are not read as source of the parent:

export default {
	...application,
	ignore: ["another-project/**"]
}