Repository navigation
chore(oxlint.config): load the jsdoc and vitest JS plugins only in the overrides that use them - #11946
Conversation
…e overrides that use them
|
|
View your CI Pipeline Execution ↗ for commit d65a293
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview2 package(s) bumped directly, 23 bumped as dependents. 🟩 Patch bumps
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to This configuration change scopes JSDoc and Vitest plugins to the files using their rules while preserving the other lint plugins. No actionable merge risk was identified. Pre-merge checks |
|
size-limit report 📦
|
🎯 Changes
jsdoc-jsandvitest-jswere loaded for every file in the rootoxlint.config.ts, but their rules are only enabled in one override each.jsdoc-jsinto the**/src/**/*.{ts,tsx}override that enables the jsdoc rules.vitest-jsinto the test-file override that enablesvitest-js/valid-expect.import-js,cspell,@stylisticand the local plugin at the top level, since their rules are top-level.This matches the previous ESLint config, where the jsdoc and vitest plugins were registered in the source and test blocks.
test:oxlintoutput is the same in all 27 packages.✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact
Summary by CodeRabbit