Do our tests need to detect new "module" options?

[cspotcode]

TS 4.5 introduces --module es2022

Is there anywhere in the code where we check module configs? Or hardcode module enum values? If so, we should add tests that break whenever TS adds new module options we have not accounted for. That way our nightly tests will warn us when we may need code changes.

---

We need to prove that swc ModuleKind mapping includes relevant values, and that swc properly classifies modules in node12 and nodenext mode.