knip icon indicating copy to clipboard operation
knip copied to clipboard

✂️ Find unused files, dependencies and exports in your JavaScript and TypeScript projects. Knip it before you ship it!

Results 74 knip issues
Sort by recently updated
recently updated
newest added

Similar to how the ESLint 9 pre-releases caused problems with peer dependency ranges in ESLint plugins (see https://github.com/eslint-community/eslint-utils/pull/206) the peer dependency range for `typescript` in `knip` causes problem when using...

bug

The project page mentions using knip on CI, but the documentation doesn't give any specific examples. In my case, I was introducing knip into an existing project, so I needed...

feature request

This is unfortunately undocumented like most next.js quirks but this does work if you are making an og image route handler kinda like the `opengraph-image` convention but with less magic

Please add one comment per plugin (please link to website/repo/docs), which others can then upvote using reactions like 👍 (not more comments). The idea is that you can request/upvote plugins...

plugin

I am running knip on a TS application with the following knip & jest files: knip.json ```json { "$schema": "https://unpkg.com/knip@5/schema.json", "entry": ["src/server.ts", "src/commands/command.ts", "test/**/*.ts", "!test/mocks/**/*"], "paths": { "@/src/*": ["./src/*"], "@/test/*":...

good first issue
feature request

In a lib written in JS with the type declared in an `index.d.ts` referenced in the `package.json` `types` field, knip reports `index.d.ts` as unused. It would be nice if knip...

feature request

Closes #568 PR aims to implement a reporter for generating JUnit xml. Without `--reporter-options` it will output the results to the console. By providing `path` value, the reporter will try...

Rather than just escaping `$`, escape all regex special characters in any identifiers to make sure the RegExp that is created is valid. Used the list of characters to escape...

Since Nx is more or less a replacement for good ol' scripts, I keep its project-specific configuration in `package.json`: ```jsonc { "name": "foo", "nx": { "targets": { "fun": { "executor":...

good first issue
feature request

Given this configuration: ```jsonc // nx.json { "targetDefaults": { "fun": { "executor": "nx:run-commands" } } } ``` ```jsonc // project.json { "targets": { "fun": { "options": { "command": "rimraf /"...

good first issue
feature request