feat(linter): implement n/handle-callback-err rule

[baevm]

this PR implements n/handle-callback-err rule, passes all tests from original rule

issue #493

[Copilot]

Pull request overview

This PR implements the n/handle-callback-err rule from eslint-plugin-n, which enforces proper error handling in Node.js callback functions. The rule checks whether the first parameter of a function (typically named "err" or "error") is referenced within the function body, helping developers avoid forgetting to handle errors in callback patterns.

Changes:

• Implements the HandleCallbackErr rule with configurable pattern matching (plain string or regex) for identifying error parameters
• Adds comprehensive test coverage covering various scenarios including nested callbacks, arrow functions, and custom error parameter names
• Integrates the rule into the linter infrastructure through generated enum and runner files

Reviewed changes

Copilot reviewed 3 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
crates/oxc_linter/src/rules/node/handle_callback_err.rs	New rule implementation with pattern matching, configuration parsing, and logic to detect unhandled error parameters
crates/oxc_linter/src/snapshots/node_handle_callback_err.snap	Snapshot tests showing expected diagnostic output for failing test cases
crates/oxc_linter/src/rules.rs	Adds the new rule module to the node rules collection
crates/oxc_linter/src/generated/rules_enum.rs	Generated code integrating the rule into the RuleEnum system
crates/oxc_linter/src/generated/rule_runner_impls.rs	Generated code specifying which AST node types the rule should run on

[codspeed-hq]

Merging this PR will not alter performance

✅ 4 untouched benchmarks
⏩ 51 skipped benchmarks¹

---

_{Comparing baevm:n/handle_callback_error (9ed0f41) with main (1710f56)}

Footnotes

1. 51 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. ↩

[baevm]

CI spell check is failing for test case with regex option, not sure how to fix/ignore it

[camc314]

@baevm you should be able to do // spellchecker:disable-line ?

[baevm]

@baevm you should be able to do // spellchecker:disable-line ?

ty! fixed it

[connorshea]

Is there a reason not to format this as:

Suggested change

	#[serde(deserialize_with = "deserialize_error_pattern")] Box<ErrorPattern>,
	#[serde(deserialize_with = "deserialize_error_pattern")]
	Box<ErrorPattern>,

[connorshea]

From a docs/config perspective this looks fine to me now.