ci(miri): add oxc_transformer to paths

[Dunqing]

No description provided.

[Dunqing]

• refactor(traverse): simplify pointer manipulation and improve readability #9162
• ci(miri): add oxc_transformer to paths #9211 👈 (View in Graphite)
• feat(ast)!: remove AstBuilder::copy #9210
• refactor(transformer/jsx): simplify and remove all AstBuilder::copy usages #9209
• 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.

[overlookmotel]

I'm not sure if we should do this.

Miri doesn't examine the whole crate, it just runs the tests and checks for any undefined behavior in those tests. What we're worried about (or at least I'm worried about) is the soundness of Traverse, but the tests in oxc_transformer crate are almost all unit tests which don't use Traverse, so they don't exercise the code paths that we want Miri to look at.

More testing is always better than less, but Miri is phenomenally slow to run. So I think we should only deploy Miri in quite a targeted way.

Let me think about this please...