feat(linter): use oxlint via napi

[camc314]

No description provided.

[camc314]

• feat(linter): use oxlint via napi #11779 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #11779 will improve performances by 15.14%

_{Comparing c/06-17-feat_linter_use_oxlint_via_napi (9f3254f) with main (9a2548a)}

Summary

⚡ 1 improvements
✅ 33 untouched benchmarks
⁉️ 4 dropped benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	BASE	HEAD	Change
⁉️	linter[RadixUIAdoptionSection.jsx]	2.6 ms	N/A	N/A
⁉️	linter[binder.ts]	149.9 ms	N/A	N/A
⁉️	linter[cal.com.tsx]	1.2 s	N/A	N/A
⁉️	linter[react.development.js]	54.9 ms	N/A	N/A
⚡	mangler[cal.com.tsx]	3.5 ms	3.1 ms	+15.14%

[Boshen]

Maybe we should have two builds, a bin and a lib build 🤔

[camc314]

Maybe we should have two builds, a bin and a lib build 🤔

on the npm side? or the rust side?

that's what i've got on the rust side.

the end goal, i think was going to be:

#[napi]
fn linter(/* some args all optional*/) {}


fn main() {
    linter(NOne, None...)
}

that way you can still use cargo build --bin oxlint while also be able to invoke from the node side