Optimize Oxlint integration and release v3.4.0 by levibuzolic · Pull Request #58 · levibuzolic/eslint-plugin-no-only-tests (original) (raw)
Navigation Menu
Provide feedback
Saved searches
Use saved searches to filter your results more quickly
Appearance settings
Conversation
Summary
- ship this as
v3.4.0 - optimize the existing Oxlint integration by adopting Oxlint's performance-focused
createOnceAPI while keeping ESLint compatibility and zero runtime dependencies - migrate the repo from Yarn + Biome/Prettier to Bun + Oxlint/Oxfmt and update CI/docs accordingly
- add real CLI E2E coverage for both ESLint and Oxlint, including
--fixbehavior and a package-contents guard
What Changed
- rewrote rules/no-only-tests.js so it exposes both:
createOncefor Oxlint's optimized APIcreatefor ESLint compatibility
- kept Oxlint configuration the same for users: the plugin still works through
jsPlugins - removed the dependency on
@oxlint/plugins; the final implementation is dependency-free at runtime - bumped the package version to
3.4.0 - kept the published Node engine range at
>=5.0.0 - switched repository tooling from Yarn to Bun
- replaced Biome/Prettier usage with Oxlint and Oxfmt
- updated GitHub Actions to use Bun, newer action versions, and a modern Node test matrix
- added CLI-level E2E tests for:
- ESLint diagnostic counts under multiple configs
- Oxlint diagnostic counts under multiple configs
--fixbefore/after file assertions for both tools
- moved test code into
test/and added a package-content check to ensure test assets are never included in the published tarball - refreshed README, changelog, releasing docs, and package metadata to match the new setup
Testing
bun run typecheckbun run lintbun run format:checkbun run test
levibuzolic changed the title
Add Oxlint compatibility adapter and bump to v4 Optimize Oxlint integration and bump to v4
levibuzolic changed the title
Optimize Oxlint integration and bump to v4 Optimize Oxlint integration and release v3.4.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})