@haoqunjiang I have not used oxlint much myself, so I have some naive questions

If I understand correctly, this adds oxlint but no configuration files. Shouldn't we provide an example config a bit more complete thancorrectness? For example, I'm not sure what should be done for Vue files now that oxlint supports some rules, but not all. Same question for TS projects: what should be configured? Is it automatically done? Or should it be done manually (and then documented)?

I'm not against making it the default, but as it is currently an addition more than a replacement, it feels like this just adds more maintenance burden in created project, with slightly unclear interactions between the various tools.

I opened#875 to simplify the generation process (it's really hard to make changes with the current implementation) and added.oxlintrc.json in the generated projects.

I had thought oxlint should be the default zero-config linting tool, as it's so fast and prioritizedcorrectness rules in its early development.
But yeah, it's a bit hard to ignore the inherent complexity now. Yet it only supports JSON configurations, so I don't have a good idea to fix that.

As for TypeScript, I've tried my best to encapsulate the complexities into@vue/tsconfig, but the generated tsconfigs haven't been documented well, which could be improved before making TS the default language.