`resolveJsonModule: true`

[fregante]

May be time? Import attributes are live: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import/with#browser_compatibility

• Node.js 20.10 (Release date: 2023-11-22)
• Chrome 123 (Release date: 2024-03-19)
• Safari 17.2 (Release date: 2023-12-11)
• Firefox 138 (Release date: 2025-04-29)

Some useful info: https://www.typescriptlang.org/docs/handbook/modules/reference.html#the-module-compiler-option

[fregante]

Node 18 reached EOL two months ago, so there might be more changes possible, like ES2024?

[sindresorhus]

I don't think resolveJsonModule is relevant for the standardized with {type: 'json'}.

[fregante]

What does that mean? What else is relevant?

[sindresorhus]

resolveJsonModule is a legacy option used to enable JSON with require/import without any attribute. The with {type: 'json'} should just work, in theory.

[fregante]

resolveJsonModule is a legacy option

Not yet. They've supported import attributes since v5.3 but you still have to enable it:

{
  "compilerOptions": {
    "target": "ES2022",
    "module": "nodenext",
    "moduleResolution": "nodenext"
  }
}

https://stackblitz.com/edit/vitejs-vite-pss7sdhl?file=test.ts,package.json,tsconfig.json&terminal=dev

What we're missing is a way for TSC to warn against attribute-less imports, but that shouldn't stop you from using something that has been available for years everywhere. Sounds more like a lint rule.

That's why I'm asking what do you need to enable this option?

At any rate, the comment is outdated/incorrect

tsconfig/tsconfig.json

Line 13 in 2cb6725

"resolveJsonModule": false, // ESM doesn't yet support JSON modules.

[fregante]

The with {type: 'json'} should just work, in theory.

I asked for updates in https://togithub.com/microsoft/TypeScript/issues/54929#issuecomment-3071798122

[sindresorhus]

From what I can remember, the problem with using the flag is that each consumer also need the flag, which creates a lot of problems. It would be better to just wait for it to be available without a flag.

[zanminkian]

See: microsoft/TypeScript#61805 (comment).

TS core team member memtion that:

This PR also makes node20 and nodenext imply resolveJsonModule. This change will be backported to node16 and node18 in TypeScript 6.0.

I don't think we should add resolveJsonModule: true for ESM-only projects.

We should remove resolveJsonModule from tsconfig.json. (Current is resolveJsonModule: false)