refactor(linter/plugins): add parse function

[overlookmotel]

Add function to parse source text into raw transfer buffer to apps/oxlint. It's required for rule tester (#16206).

[overlookmotel]

• feat(linter/plugins): introduce RuleTester #16206
• refactor(linter/plugins): add parse function #16240 👈 (View in Graphite)
• refactor(linter/plugins): store messageId in diagnostics #16296
• refactor(linter/plugins): move placeholder replacement into own function #16302
• 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 Performance Report

Merging #16240 will not alter performance

_{Comparing 11-28-refactor_linter_plugins_add_parse_function (26e3bdd) with main (10a793e)¹}

Summary

✅ 42 untouched
⏩ 3 skipped²

Footnotes

1. No successful run was found on 11-30-refactor_linter_plugins_store_messageid_in_diagnostics (72b48e7) during the generation of this report, so main (10a793e) was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[graphite-app]

Merge activity

• Nov 30, 11:50 PM UTC: overlookmotel added this pull request to the Graphite merge queue.
• Nov 30, 11:57 PM UTC: Merged by the Graphite merge queue.

[camc314]

is this code the same as oxc parser napi package? should the code between the two be shared?

[overlookmotel]

It's mostly the same, but has some differences to integrate with the slight difference between oxc-parser and oxlint (Oxlint doesn't deal with the module record).

Is there a way to have code shared between the 2 packages, without a dependency? Maybe if we convert napi/parser to TS, and build it with TSDown. (speaking of converting, yes, I'm a convert to TS)

[camc314]

Is there a way to have code shared between the 2 packages, without a dependency?

best way it just to have it as a dep, we can make sure that tsdown bundles it so there'll be no runtime overhead