`"module": "node16"` gives contradictory error about import assertions

[kidonng]

Bug Report

🔎 Search Terms

module node16 import assertions

🕗 Version & Regression Information

Happened in 4.8.2, also 4.7.4 and 4.8 beta in playground.

⏯ Playground Link

Playground link with relevant code

💻 Code

const file = "foo.json"
const test = await import(file, {assert: {type: 'json'}})
export {}

🙁 Actual behavior

Dynamic imports only support a second argument when the '--module' option is set to 'esnext', 'node16', or 'nodenext'.

🙂 Expected behavior

No error

[andrewbranch]

This is not a TypeScript issue, but a Playground issue—so while the symptom is slightly different, it’s a duplicate of #49842. Until fixed, you have to refresh the playground page after switching module 😕

[fatcerberus]

@andrewbranch Still repros after setting Module to Node16 and refreshing. Changing to NodeNext and refreshing makes the error go away. So this does seem to be as described, node16 doesn’t support dynamic import assertions, in contradiction of the error message.

[kidonng]

Sorry, I really should have stated this also happens locally:

I noticed the Playground has some funky issues, but I assume you already know abou that.