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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@nesvel/knip-config

v1.0.3

Published

Shared Knip configuration for unused code detection in monorepos

Readme

@nesvel/knip-config

Shared configuration presets for Knip, the analyzer that finds unused files, exports, and dependencies in JavaScript/TypeScript projects.

Features

  • 🎯 Multiple Presets: base, library, vite, nextjs, workspace
  • 📦 One-command installation: Copy preset to your project
  • ⚙️ Customizable: Override any configuration as needed
  • 🚀 Production-ready: Opinionated defaults for common setups

Installation

pnpm add -D @nesvel/knip-config knip
# or
npm i -D @nesvel/knip-config knip

Quick start

Using Installation Script (Recommended)

Install a preset using the built-in command:

# Install base preset (simple library)
pnpm knip-install

# Or specify a preset
pnpm knip-install library
pnpm knip-install vite
pnpm knip-install nextjs
pnpm knip-install workspace

Manual Installation

Copy a preset to your project root:

cp node_modules/@nesvel/knip-config/src/presets/base.json knip.json

Available Presets

base

Simple library with a single entry point (src/index.ts). Best for basic TypeScript libraries.

library

Library with multiple entry points and test framework support. Includes Jest/Vitest configuration.

vite

Vite/React application with proper handling of index.html, main.tsx, and Vite config.

nextjs

Next.js application supporting both Pages Router and App Router.

workspace

Monorepo/workspace configuration with patterns for apps/*, packages/*, and packages/tools/*.

Usage

Add scripts to your package.json:

{
  "scripts": {
    "knip": "knip",
    "knip:fix": "knip --fix",
    "knip:strict": "knip --strict",
    "knip:install": "knip-install"
  }
}

Run knip:

# Check for unused code
pnpm knip

# Auto-remove unused dependencies
pnpm knip --fix

# Strict mode (fails on any issue)
pnpm knip --strict

Customization

After installing a preset, you can customize knip.json as needed:

{
  "$schema": "https://unpkg.com/knip@5/schema.json",
  "entry": ["src/index.ts"],
  "project": ["src/**/*.{ts,tsx}"],
  "ignore": [
    "**/node_modules/**",
    "**/dist/**",
    "**/my-custom-ignore/**"
  ],
  "ignoreDependencies": [
    "my-special-package"
  ]
}

CI/CD Integration

Add Knip to your CI pipeline:

# .github/workflows/ci.yml
- name: Check for unused code
  run: pnpm knip --production

Or add it to your package.json:

{
  "scripts": {
    "ci": "pnpm typecheck && pnpm lint && pnpm test && pnpm knip --production"
  }
}

Recommendations

  • ✅ Run pnpm knip locally before committing to keep dependencies tidy
  • ✅ Use --fix cautiously; review changes in PRs
  • ✅ Add pnpm knip --production to CI to catch issues early
  • ✅ Start with a permissive config and tighten over time
  • ✅ Use ignoreExportsUsedInFile for type-only exports

Troubleshooting

False positives

If Knip reports something as unused but it's actually used:

  1. Add it to ignore or ignoreDependencies in knip.json
  2. Check if the file/export is actually being imported correctly
  3. Use includeEntryExports: true to mark entry point exports as used

Config not working

Make sure:

  • knip.json exists in your project root
  • Patterns use glob syntax (e.g., src/**/*.ts not src/)
  • Entry points are correctly specified

License

MIT © Nesvel