Skip to content

chore(deps): prune stale knip config entries#8165

Draft
EvilGenius13 wants to merge 1 commit into
mainfrom
jf/knip-config-prune
Draft

chore(deps): prune stale knip config entries#8165
EvilGenius13 wants to merge 1 commit into
mainfrom
jf/knip-config-prune

Conversation

@EvilGenius13

@EvilGenius13 EvilGenius13 commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

What

Prunes 14 stale entries from the inline knip config in root package.json. Pure config cleanup — no source or behavior changes.

Why

pnpm knip was emitting 16 configuration hints flagging its own config as stale. All 14 targeted entries were verified obsolete:

  • 8 ignoreDependencies were suppressing nothing — each dep is now genuinely used (direct imports, generated GraphQL client files, or @testing-library/react peer deps). Since knip's dependencies rule is error, a truly-unused dep would have failed the run; it stays green.
  • 5 entry patterns were dead: 3 match zero files (docs-shopify.dev/**/*.ts, docs/api/cli-kit/**/*.js, plugin-cloudflare commands/hooks) and 2 duplicate knip's built-in defaults (vite.config.ts, graphql.config.ts).
  • 1 ignore (packages/e2e/scripts/**) nested inside the already-ignored packages/e2e workspace.

- Remove 8 obsolete `ignoreDependencies` entries now genuinely used (direct imports, generated GraphQL clients, or @testing-library/react peer deps) across app, cli-kit, store, organizations, ui-extensions-server-kit, ui-extensions-test-utils.
- Remove 5 dead/redundant `entry` patterns: non-matching globs (docs-shopify.dev/**/*.ts, docs/api/cli-kit/**/*.js, plugin-cloudflare commands/hooks) and knip built-in defaults (vite.config.ts, graphql.config.ts).
- Remove 1 redundant `ignore` (packages/e2e/scripts/** — packages/e2e is already in ignoreWorkspaces).
- No behavior change: knip still exits 0 with zero findings; config hints drop 16 -> 2 (remaining 2 are pre-existing ./assets/** packaging refs, untouched).
@github-actions github-actions Bot added the no-changelog This PR doesn't include a changeset entry. Is an internal only change not relevant to end users. label Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog This PR doesn't include a changeset entry. Is an internal only change not relevant to end users.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant