【发布时间】:2022-12-28 00:37:40
【问题描述】:
Typescript is transpiled to JavaScript, so a module routes.ts is converted into routes.js in the directory that tsc puts it. If another module imports names (e.g., "router") from a module, we leave off the suffix as in:
import { router } from './routes'
This worked fine until node stopped using .js as a default suffix. Starting in node V16 (or maybe earlier ?), it was necessary to add the flag
--es-module-specifier-resolution=node in order to run the transpiled code with node.
In later nodeJS versions this option was downgraded by being silently converted into
--experimental-specifier-resolution=node which was then dropped altogether in NodeJS v19.
Now in NodeJS v19, one is supposed to use "custom loaders" instead. Is it really that hard to run transpiled TypeScript code? What is the recommended approach?
【问题讨论】:
-
Since the ESM spec requires file extensions with
import, I presume nodejs is just moving in the direction of the spec. This sounds like something the TypeScript compiler should fix. I wonder if this is being discussed in the TypeScript world. Have you looked through the TypeScript compile options to see if there's an option to fix this (providing an extension in the generated code)? Or looked where TypeScript issues are discussed? -
Are you using ES modules or not? If yes, then include the
.jsextension in your imports and update your TS config as necessary.
标签: node.js typescript