chore: add oxlint to lint-staged configuration for improved linting

[lyzno1]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @lyzno1, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the project's code quality enforcement by introducing oxlint into the lint-staged workflow. This addition aims to provide faster and potentially more comprehensive linting feedback during the pre-commit phase, complementing the existing ESLint setup and ensuring a higher standard of code consistency and error detection before changes are committed.

Highlights

• Oxlint Integration: The oxlint linter has been integrated into the lint-staged configuration for JavaScript and TypeScript files.
• Pre-commit Hook Enhancement: The oxlint command will now run as part of the pre-commit hook, executing before eslint for files matching **/*.{js,jsx,ts,tsx,mjs}.
• Configuration: Oxlint will use the configuration specified in .oxlintrc.json.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds oxlint to the lint-staged configuration. While this aligns with other linting scripts in the project, my review points out that this creates a redundant check because eslint is already configured to run oxlint rules via a plugin. I've suggested a simplification to make the pre-commit hook more efficient by removing the redundant command.