-
Notifications
You must be signed in to change notification settings - Fork 162
chore: migrate from ESLint to oxlint with @eggjs/oxlint-config #68
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
chore: migrate from ESLint to oxlint with @eggjs/oxlint-config #68
Conversation
Co-authored-by: fengmk2 <[email protected]>
Co-authored-by: fengmk2 <[email protected]>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
commit: |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Join our Discord community for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
This PR migrates the project from ESLint to oxlint using the official
@eggjs/oxlint-configconfiguration. The migration maintains full compatibility with the existing codebase while leveraging oxlint's superior performance and modern rule set.Changes Made
Dependencies
eslint@^8.54.0andeslint-config-egg@^13.0.0(deprecated ESLint v8)oxlint@^1.11.1and@eggjs/oxlint-config@^1.0.0Configuration
.eslintrcconfiguration file.oxlintrc.jsonextending@eggjs/oxlint-configwith compatibility overridesScripts
lintscript fromeslint src test --ext tstooxlint src testpretest,preci) continue to work unchanged--fixflag continues to work for auto-fixing issuesBenefits
@eggjs/oxlint-configfor consistent standardsCompatibility
The migration includes carefully tuned rule overrides in
.oxlintrc.jsonto ensure full backward compatibility with the existing codebase. All tests pass (96 passing, 1 pending) and the build process remains intact.Verification
npm run lint- 0 errors, 0 warningsnpm test- All 96 tests passingnpm run prepublishOnly- Successful buildnpm run preci- All checks pass💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.