feat: add oxlint support

[kaiiiiiiiii]

Closes #166

Added oxlint as a linter option :)

• Dropped in the default config that oxlint --init generates.
• Added prettier since oxc doesn’t ship a formatter yet (still WIP).

[kaiiiiiiiii]

Added @prettier/plugin-oxc as recommended by oxc (https://oxc.rs/docs/guide/usage/formatter.html) and merged latest main version

[kaiiiiiiiii]

Any feedback @jherr?

[jherr]

Any feedback @jherr?

Yeah, my issue is with the .oxlintrc.json (which should be _dot_oxlintrc.json but that's not the issue). Does it need to be that large? Is there some widely used default for it?

[kaiiiiiiiii]

Any feedback @jherr?

Yeah, my issue is with the .oxlintrc.json (which should be _dot_oxlintrc.json but that's not the issue). Does it need to be that large? Is there some widely used default for it?

Hey @jherr! Thanks for taking a look at this.

Regarding the .oxlintrc.json size and filename:

On the filename: You're absolutely right about the naming convention. My bad. I'll fix that.

On the file size: The current config is indeed what oxlint --init generates by default. However, you raise a valid point about whether we need all of it.

The generated config is comprehensive because it explicitly lists all available plugins and rules with their default settings. For a project template, we have a few options:

1. Minimal approach: We could strip it down to just the essentials:

{
  "plugins": ["react", "unicorn", "typescript", "oxc"],
  "categories": {
    "correctness": "error"
  }
}

2. Zero-config approach: Actually rely on oxlint's zero-config defaults and omit the config file entirely, since oxlint works out of the box without any configuration.

3. Keep the full config: Provides visibility into all available options for users who want to customize.

To reduce file size I would personally lean toward option 1 (minimal config) since it:

• Keeps the file manageable
• Shows the basic structure for users who want to extend it
• Leverages oxlint's smart defaults for everything else
• Aligns better with oxlint's "zero-config" philosophy

What do you think? I'm happy to slim it down to a minimal config that just enables the plugins and maybe a few project-specific overrides if needed or delete the file entirely.

[jherr]

Cool. Hearing that it's the --init output makes me really happy and want to skew that way. That being said, have you tried this with building a project? Do we get linting errors based on the setup on our existing code?