Repository navigation
chore: clean up stale monorepo tooling config (AI-assisted) #12773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
2645fdf
99a8865
7180bd7
07f4d27
863b4f5
1126b25
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Apply the fork exclusion in production mode.
When
pnpm lint:knip:productionruns, Knip uses entry patterns with a trailing!. The theme entry pattern has that suffix, but this exclusion does not. The fork modules therefore remain entry files in the production analysis, which skips unused exports in entry files by default. Add the suffix to the exclusion. (knip.dev)Proposed change
📝 Committable suggestion
🤖 Prompt for AI Agents