panics after root node changes

[camc314]

Regression from: 228cff5

ecosystem CI workflow: https://github.com/oxc-project/oxlint-ecosystem-ci/actions/runs/16142683018/job/45553773604

[camc314]

[crates/oxc_linter/src/rules/typescript/triple_slash_reference.rs:110:13] ctx.file_path() = "/Users/cameron/github/rolldown/rolldown/examples/hmr-raw/src/runtime.d.ts"

thread '<unnamed>' panicked at crates/oxc_linter/src/rules/typescript/triple_slash_reference.rs:111:13:

This appears to be triggered by .d.ts files.

[camc314]

@overlookmotel or @Dunqing why do we not set the program node in semantic (or visit the program for that matter) when doing semantic analysis on TS definition files?

[ulrichstark]

Oh whoops sorry. When I did this change, I assumed that lint rules are always run on files with at least the Program node available.

These are the lint rules triggering a panic in the ecosystem workflow:

• unicorn/no_empty_file
• eslint/sort_imports
• typescript/triple_slash_reference

[camc314]

yeah don't worry about it, that's what those CI tests are for! we will fix it before we release.

i need to understand why we don't make nodes for TS declaration files before we decide how to fix it. (It seems pretty reasonable that we might want to lint on .d.ts files, hence have semantic analysis for them

[overlookmotel]

I'm afraid I can't answer that one. I've wondered the same thing myself.

[Dunqing]

Fixed in #12193