Lars

@webpro.nl

2721 Followers 284 Following

Independent developer/architect. JavaScript/TS, DX, automation, tooling, performance & OSS. 🏡 https://webpro.nl 🦋 https://webpro.blue 🧑‍💻 https://github.com/webpro ✂️ https://knip.dev

Terminal displaying output of running knip with experimental "cycles" reporter. In this case there are two circular dependencies in the prettier repository.

dependency graph of knip v6.6.0 showing only 18 dependencies in total (i.e. including transitive dependencies)

Screenshot of my personal Raycast bookmarks extension: open bookmark.

screenshot of a knip run in the typescript repo, after deleting the checker.ts file. resulting in unresolved import and unused exports.

Bluesky app opening screen, a drawing of happy and playful people being together in small groups in a large green park under a... 🥁... blue sky.

✻ Discombobulating...

Screenshot of Raycast extension, showing a filtered list of repositories matching a fuzzy "unb" search. The actions panel with a list of sub paths for selected repository is open.

Image of water, grass, trees and blue sky

Screenshot of Knip printing configuration hints for unused ignore patterns in knip.json. For instance, because they're already covered by .gitignore entries.

Sad Escobar

Screenshot from someone on Twitter saying:

"I'd love tips on how you all handle code complexity when AI coding the same project for months. I end up spending like 7-80%% of the time just cleaning up and refactoring and deleting things.

There has to be a better way."

Reproduction url:

not needed, just gonna tell you how to fix it

Screenshot of a package on npmx.dev, highlighting this text card:

1 deprecated dependency

@types/parse-path@7.1.0

This is a stub types definition. parse-path provides its own type definitions, so you do not need this installed.

Chart of "star history" for the Knip repo (from 0 to over 10K in 39 months)

Snippet of knip config:

{
"$schema": "https://unpkg.com/knip@5/schema.json",
"entry": ["src/router.tsx"],
"tailwind": { "entry": ["src/styles.css"] },
"project": ["src/**/*.{js,jsx,ts,tsx,mdx,css}"]
}

Not everything needs an alt text, does it 😅

Screenshot of `knip --trace-file string.ts` in the terminal

Screenshot of the Knip extension in VS Code showing the "problem" tab with a list of issues reported by Knip

Ha! That's meta as hell — developing Knip while using Knip's own VS Code extension to help you develop it. 🔄

The ultimate dogfooding setup. If you find issues with the extension while working on the codebase, you can fix them in real-time since it's symlinked.

"No where in here does it say 'Thou shall not fart.'"

Screenshot of terminal to demonstrate the commands from the post:

gh-pr-co 1
echo "make a change" >> README.md
git commit -am "fixes"
git push pr1 --no-follow-tags

Photo of a newspaper article. The last, highlighted paragraph reads:

"If you want, I can also create an even snappier "front-page style" version with punchy one-line stats and a bold, info-graphic-ready layout — perfect for maximum reader impact. Do you want me to do that next?"

Show Active File Only

Like I said, too much to unpack! Rest assured it will happen.

const largeSet = new Set();

[...largeSet].map(mapFn);

Array.from(largeSet).map(mapFn);

Array.from(largeSet, mapFn);

Chart showing 4142496 weekly dowmloads

Hoping for rain

Screenshot of a Knip plugin idea: showing basically the same as you would get for a manual "Find All References", but directly on hover of an exported value or type

Screenshot with ideas for Knip plugin that shows links to import locations of an export in the code, and a sidebar panel with all imports and exports

Second raw demo of unused things that Knip detects, including some navigation between imports and exports in VS Code

Quick & rough demo of navigation between imports and exports in VS Code

ignoreIssues: Ignore specific issue types for specific file patterns. Keys are glob patterns and values are arrays of issue types to ignore for matching files. This allows ignoring specific issues (like unused exports) in generated files while still reporting other issues in those same files.

excerpt from the linked article, it reads:

what knip nailed, and where it didn’t

Good at common React and server app entry points, and lots of config conventions. Not great when usage is indirect or only happens in scripts or CI. That’s fine. Humans still have jobs.

final part of npm weekly downloads chart, crashing down as numbers for last few days haven't been accumulated

Table of recent pull requests in July that have lots of lines removed using Knip (top 10 has 9k up to 60k lines removed)

Gandalf from LOTR looking determined

Screenshot of SwiftKey stats screen with e.g. flow distance and count

Screenshot of Knip configuration (in VS Code) and a Knip run (in a terminal) showing the entry files that can be removed: mostly configuration files for tools like Vite, Vitest, Playwright, PostCSS, ESLint, Storybook and Prisma

Screenshot of three charts next to each other:

1) previous situation where memory usage kept growing
2) current default situation with some garbage collection, and faster
3) with the --isolate-workspaces flag, twice as slow but keeping memory in check with more aggressive garbage collection

Screenshot of a terminal showing the default knip reporter with tables and truncated cell values, so they always take up one line per issue

Meme "feels good man"

Screenshot of GitHub PR git summary of changes: +311 and -6353 (i.e. lots of code was removed using Knip)

Screenshot of projects using Knip, as listed on https://knip.dev/#trusted-by-the-worlds-best-software-teams

Screenshot of Knip on npm showing over half of weekly downloads comes from the latest versions, suggesting lots of those are coming from usage like `npx knip`

Screenshot of an example package.json with "exports" entries that Knip maps to source files and then automatically adds as entry files

Screenshot of seemingly doubly-posted reply to a post (the reply was sent only once)

Screenshot of WhatsApp displaying emoji domain name verbatim