• feat(linter): load custom JS plugins configured in overrides #12324 👈 (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.

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

CodSpeed Instrumentation Performance Report

Merging #12324 will not alter performance

_{Comparing c/07-16-feat_linter_load_custom_js_plugins_configured_in_overrides (4f50750) with main (21e8f0a)}

Summary

✅ 34 untouched benchmarks

Merge activity

• Jul 16, 4:10 PM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Jul 16, 4:17 PM UTC: overlookmotel added this pull request to the Graphite merge queue.
• Jul 16, 4:26 PM UTC: Merged by the Graphite merge queue.

Hi @camc314 what an amazing news in this release 💯
I was trying directly based on the e2e test you written to use my first js plugin in the 1.7.0 but got the following:

 × Failed to load external plugin because no external linter was configured. This means the Oxlint binary was executed directly rather than via napi bindings.

Based on my understanding it is because we are needing the following https://github.com/oxc-project/oxc/blob/main/napi/oxlint2/package.json do you think a preview release could be made on npm?
This would be really awesome for trying around 🙌

Thank you. We are still working to finalize the feature, and fix some of the missing pieces. once that work is done, we will do a preview release allowing you to try it out.