Migrate from eslint to oxlint with @eggjs/oxlint-config #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR migrates the project from eslint to oxlint using the official
@eggjs/oxlint-config
configuration, providing faster linting performance while maintaining code quality standards.Changes Made
Dependencies:
eslint
andeslint-config-egg
from devDependenciesoxlint
and@eggjs/oxlint-config
as devDependenciesConfiguration:
.eslintrc
and.eslintignore
files.oxlintrc.json
extending@eggjs/oxlint-config
with:describe
,it
,afterEach
)Scripts:
lint
script fromeslint src test
tooxlint src test
Benefits
@eggjs/oxlint-config
Verification
The migration has been thoroughly tested:
npm run ci
) executes successfullynpm run prepublishOnly
) works correctlyThis is a drop-in replacement that improves developer experience through faster feedback cycles while maintaining the same code quality standards.
💡 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.