Fix resolveJsonModule default for nodenext module

[Copilot]

resolveJsonModule was not defaulting to true when module is nodenext, causing errors when importing JSON files without explicitly setting the option.

// tsconfig.json: { "compilerOptions": { "module": "nodenext" } }
import pkg from './package.json' with { type: 'json' };
// tsc 5.9.3: ✅
// tsgo before fix: "Consider using '--resolveJsonModule' to import module with '.json' extension."

Changes

• Fixed the switch case in GetResolveJsonModule() to include ModuleKindNodeNext alongside ModuleKindNode20, and removed ModuleKindESNext which shouldn't have been there per the TypeScript implementation

Original prompt

---

This section details on the original issue you should resolve

<issue_title>resolveJsonModule is not defaulted to true when module is nodenext</issue_title>
<issue_description>## Steps to reproduce

TS:

import packageJson from './package.json' with { type: 'json' };

Result:

"module":	tsc 5.9.3	tsgo 7.0.0-dev.20260203.1
"node20"	✅	✅
"nodenext"	✅	Consider using '--resolveJsonModule' to import module with '.json' extension.

<agent_instructions>Cross-compare the linked TypeScript and typescript-go PRs to look for differences to help find a fix.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes resolveJsonModule is not defaulted to true when module is nodenext #2652

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR fixes a bug where resolveJsonModule was not defaulting to true when the module compiler option is set to nodenext, causing errors when importing JSON files without explicitly setting the option.

Changes:

• Added ModuleKindNodeNext to the switch case in GetResolveJsonModule() to ensure it defaults to true alongside ModuleKindNode20 and ModuleKindESNext