Dynamically importing JSON should require import attribute with node16/nodenext

[kirkwaiblinger]

🔎 Search Terms

dynamic import, import attribute, resolveJsonModule,

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about TS 5.7's new checks around importing JSON

⏯ Playground Link

https://github.com/kirkwaiblinger/repro-TS-dynamic-json-import-validation

💻 Code

// module: node16/nodenext, resolveJsonModule
// .cts or .mts, it doesn't matter.

async function main() {
    const somethingDynamic = await import('./someThing.json');
    console.log('dynamically imported JSON:', somethingDynamic);
}

main();

export {}

🙁 Actual behavior

No error, even though this is a runtime error in nodejs.

🙂 Expected behavior

Error because dynamic import('./someThing.json') requires import attribute.

Additional information about the issue

Unlike the static import case, this is the case for both commonjs and esm outputs, since import() is available in commonjs modules in node and has the same semantics there as the ESM import (and therefore TS doesn't transform the import() statement to a Promise.resolve(require())).

[kirkwaiblinger]

Note - obviously not all dynamic imports even can be analyzed, but TS does already analyze these sorts of dynamic imports where a literal is provided to both a) provide type definitions in the file, and b) copy the JSON file to the output dist. If it's doing that, I think it should also demand the import attributes (whereas obviously I wouldn't expect this for import(arbitraryString)).