Environment

• Operating System: Windows_NT
• Node Version: v24.4.1
• Nuxt Version: 4.0.0
• CLI Version: 3.26.2
• Nitro Version: 2.12.0
• Package Manager: npm@11.4.2
• Builder: -
• User Config: compatibilityDate, devtools, srcDir, modules, sourcemap, routeRules, runtimeConfig, vite
• Runtime Modules: @nuxt/eslint@1.5.2, nuxt-compile-markdown@0.1.1
• Build Modules: -

Reproduction

I don't have time to create a reproduction right now, but let me know if I should add one later.

Describe the bug

Title says it. This issue makes it so enabling TypeScript checking (// @ts-check at the top of the file) for eslint.config.js has no effect.

This is easily fixable by simply adding "../eslint.config.*" to the include array of .nuxt/tsconfig.node.json. But it may be worth considering using a broader glob to include other top-level JS files in general, such as prettier.config.js.

Additional context

I didn't run into this issue before Nuxt v4.0.0, since previously "../**/*" was in the TS config include. Now that TS configs are more granular, that's no longer an acceptable solution.