not even the most simple use-case about ts-node

[Bjoren]

Adding to this, I can't get ts-node to work at all with ESM.

A brand new project with a package.json:

{
  "type": "module",
  "dependencies": {
    "ts-node": "^10.9.1",
    "typescript": "^5.2.2"
  }
}

... and a tsconfig.json:

{
  "type": "module",
  "compilerOptions": {
    "target": "ES2022",
    "module": "ES2022"
  },
  "ts-node": {"esm": true}
}

Refuses to run script.ts

console.log("Hello world")

... with TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for <path>\project\script.ts

Very non-descriptive error message.

[AndreLeifert]

Yes, confirmed: like @Bjoren, I have "type": "module" in my package.json.
Also tried with --esm on the command line as well as with ts-node-esm... whatever that is.
Same result. Do we really have to add the suffix .js to all imports?

[wolfy1339]

Duplicate of #1997