feat(linter): add cwd property to JS plugin Context

[magic-akari]

• Closes: Linter plugins: Add cwd property to Context #14777

[graphite-app]

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.

[codspeed-hq]

CodSpeed Performance Report

Merging #14814 will not alter performance

_{Comparing magic-akari:fix/issue-14777 (5980f4a) with main (1fcf56c)}

Summary

✅ 37 untouched

[Copilot]

Pull Request Overview

This PR adds a cwd (current working directory) property to the JavaScript plugin Context object, making it accessible to custom linter rules. The change threads the cwd parameter through the linting pipeline from the Rust side to the JavaScript plugin context.

Key Changes:

• Added cwd parameter to the linter's run and run_with_disable_directives methods
• Updated external linter callbacks to accept and pass through the cwd parameter
• Exposed cwd as a property on the JavaScript Context class

Reviewed Changes

Copilot reviewed 12 out of 13 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
crates/oxc_linter/src/lib.rs	Added cwd parameter to run and run_with_disable_directives methods and passed it to external rule execution
crates/oxc_linter/src/external_linter.rs	Updated ExternalLinterLintFileCb type signature to include cwd parameter
crates/oxc_linter/src/service/runtime.rs	Updated calls to linter methods to include me.cwd
apps/oxlint/src/run.rs	Updated JsLintFileCb type to include cwd in function arguments
apps/oxlint/src/js_plugins/external_linter.rs	Updated callback wrapper to accept and forward cwd parameter
apps/oxlint/src-js/plugins/lint.ts	Added cwd parameter to lintFile and lintFileImpl functions with validation
apps/oxlint/src-js/plugins/context.ts	Added cwd property to InternalContext interface and Context class with getter
apps/oxlint/src-js/cli.ts	Updated wrapper function to include cwd parameter
tasks/benchmark/benches/linter.rs	Added path as cwd argument to linter.run call
napi/playground/src/lib.rs	Added Path::new(".") as cwd argument to linter run call
apps/oxlint/test/fixtures/context_properties/plugin.ts	Added test that reports the cwd value
apps/oxlint/test/fixtures/context_properties/output.snap.md	Updated snapshot with expected output including cwd reports

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[camc314]

can we not use process.cwd?

passing across the cwd for every file we need to lint feels expensive, especially as the cwd never chanegs (as far as i know)

[camc314]

I looked at eslint's implementation, and it just uses process.cwd() (but can be overridden via cli arguments).

We don't support CLI arguments, for overriding the current working directory, so we can just use process.cwd() on the JS side

refs:
https://github.com/eslint/eslint/blob/43a5f9e36f1aade16f81fc49ef4b333660faadab/lib/linter/linter.js#L1358
https://github.com/eslint/eslint/blob/43a5f9e36f1aade16f81fc49ef4b333660faadab/lib/linter/linter.js#L1274

[magic-akari]

I looked at eslint's implementation, and it just uses process.cwd() (but can be overridden via cli arguments).

We don't support CLI arguments, for overriding the current working directory, so we can just use process.cwd() on the JS side

refs: https://github.com/eslint/eslint/blob/43a5f9e36f1aade16f81fc49ef4b333660faadab/lib/linter/linter.js#L1358 https://github.com/eslint/eslint/blob/43a5f9e36f1aade16f81fc49ef4b333660faadab/lib/linter/linter.js#L1274

@camc314 Thanks for the review! Just to confirm I understand correctly: You're suggesting we use process.cwd() directly in JavaScript instead of passing cwd between Rust and JavaScript for every file, right?

[camc314]

I looked at eslint's implementation, and it just uses process.cwd() (but can be overridden via cli arguments).
We don't support CLI arguments, for overriding the current working directory, so we can just use process.cwd() on the JS side
refs: https://github.com/eslint/eslint/blob/43a5f9e36f1aade16f81fc49ef4b333660faadab/lib/linter/linter.js#L1358 https://github.com/eslint/eslint/blob/43a5f9e36f1aade16f81fc49ef4b333660faadab/lib/linter/linter.js#L1274

@camc314 Thanks for the review! Just to confirm I understand correctly: You're suggesting we use process.cwd() directly in JavaScript instead of passing cwd between Rust and JavaScript for every file, right?

Yep exactly!

[camc314]

Awesome, thank you!