Add Oxlint to Editor Setup Guide

[JamesJosephFinn]

Hello Astro team! 🚀

This is a request to add a section for Oxlint to the Editor Setup Guide in the best docs in the business.

I am not usually an early adopter, but if Evan You is backing it and using it in production, then I probably can, too! On this page, they claim that:

... Oxlint can be used to fully replace ESLint in small to medium projects.

For .astro files, Oxlint supports linting of the frontmatter / component script, as well as of <script> tags. However, it does not (yet!) parse any other Astro template content.

Astro support in Oxlint was first proposed by Yagiz, Principal Engineer at Cloudflare, who also serves as a consultant for the project, together with Astro core team member @ematipico.

I have Oxlint running locally in my new project, and am pleased with it so far. Their team is highly responsive on Github, starting work on my Astro related issue within an hour, and core team member @Sysix opening a PR within 24 hours.

I replaced the VS Code/ium extension for ESLint with Oxlint's, and it is working satisfactorily.

I'm using Prettier for formatting, with a plugin provided by Prettier which delegates parsing to Oxc, as suggested in the Oxc docs, and that also has been working well.

Most importantly, I have found configuration to be a breeze as compared to my experience with ESLint. I replaced over a dozen dev dependencies with 2, so I can just get to work coding rather than configuring. 🚀

I thought the best way to express my gratitude to the Oxc team would be to open this discussion.

@sarah11918

[sarah11918]

Tagging @Princesseuh into this conversation!

[Princesseuh]

Would be cool, we have Biome and dprint in there, so might as well get Oxclint too