feat: add codemod for DEP0159 ERR_INVALID_CALLBACK replacement

[syhstanley]

Summary

Adds a codemod for DEP0159 — replaces the deprecated ERR_INVALID_CALLBACK error code with ERR_INVALID_ARG_TYPE.

• Replaces all string literal occurrences of ERR_INVALID_CALLBACK with ERR_INVALID_ARG_TYPE
• Handles error code comparisons (err.code === "ERR_INVALID_CALLBACK")
• Handles switch case labels, assert.throws expectations, .includes() checks
• Deduplicates redundant || conditions after replacement (e.g., a === "X" || a === "X" → a === "X")
• No-change behavior when file has no references to the deprecated code

Test plan

• 6 test cases covering all examples from ERR_INVALID_CALLBACK error code #411
• Error code comparison in catch block
• Test assertion with error code
• Switch statement with error codes
• String includes check
• Duplicate condition deduplication
• No-change test (no ERR_INVALID_CALLBACK references)

Closes #411

🤖 Generated with Claude Code

[AugustinMauroy]

not too bad but:

for you info you have to use this structure of testing

Codemod leverages a before ("input") + after ("expected") snapshot comparison. Codemod supports 2 options:

• 👍 Single-file fixtures

  tests/
    some-test-case-description/
      input.ts
      expected.ts
    another-test-case-description/
      input.ts
      expected.ts
  

• 👎 Directory snapshot fixtures

  tests/
    input/
      some-test-case-description.ts
      another-test-case-description.ts
    expected
      some-test-case-description.ts
      another-test-case-description.ts
  

Use the Single-file fixtures option.

with this approach what if we have a code like that:

const myUtility = (file) => {
  // do something
  
  file.methode()
  
  if(file.empty) {
    console.warn("ERR_INVALID_CALLBACK");
  }
} 

I think it's will be catch we need to catch string fragment node which is on certain node idk know like that need to deep-dive