无法运行我的 Node.js Typescript 项目 TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /app/src/App.ts

Question

当我尝试在 Heroku 上启动我的应用程序时，我得到了以下堆栈跟踪。它只是一个基本的 ts.app，就像您在 ts-node 和 nodemon 中看到的那样。如果您需要更多信息，请告诉我，因为这是我的第一篇文章。我真的很想知道答案是什么。

2020-05-30T00:03:12.201106+00:00 heroku[web.1]: Starting process with command `npm start`
2020-05-30T00:03:14.405285+00:00 app[web.1]: 
2020-05-30T00:03:14.405303+00:00 app[web.1]: > discordtoornamentmanager@1.0.0 start /app
2020-05-30T00:03:14.405303+00:00 app[web.1]: > ts-node src/App.ts
2020-05-30T00:03:14.405304+00:00 app[web.1]: 
2020-05-30T00:03:14.833655+00:00 app[web.1]: (node:23) ExperimentalWarning: The ESM module loader is experimental.
2020-05-30T00:03:14.839311+00:00 app[web.1]: TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /app/src/App.ts
2020-05-30T00:03:14.839312+00:00 app[web.1]:     at Loader.defaultGetFormat [as _getFormat] (internal/modules/esm/get_format.js:65:15)
2020-05-30T00:03:14.839314+00:00 app[web.1]:     at Loader.getFormat (internal/modules/esm/loader.js:113:42)
2020-05-30T00:03:14.839315+00:00 app[web.1]:     at Loader.getModuleJob (internal/modules/esm/loader.js:244:31)
2020-05-30T00:03:14.839315+00:00 app[web.1]:     at processTicksAndRejections (internal/process/task_queues.js:97:5)
2020-05-30T00:03:14.839316+00:00 app[web.1]:     at Loader.import (internal/modules/esm/loader.js:178:17)
2020-05-30T00:03:14.847801+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-05-30T00:03:14.847998+00:00 app[web.1]: npm ERR! errno 1
2020-05-30T00:03:14.848957+00:00 app[web.1]: npm ERR! discordtoornamentmanager@1.0.0 start: `ts-node src/App.ts`
2020-05-30T00:03:14.849050+00:00 app[web.1]: npm ERR! Exit status 1
2020-05-30T00:03:14.849172+00:00 app[web.1]: npm ERR! 
2020-05-30T00:03:14.849254+00:00 app[web.1]: npm ERR! Failed at the discordtoornamentmanager@1.0.0 start script.
2020-05-30T00:03:14.849337+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-05-30T00:03:14.854859+00:00 app[web.1]: 
2020-05-30T00:03:14.854998+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-05-30T00:03:14.855069+00:00 app[web.1]: npm ERR!     /app/.npm/_logs/2020-05-30T00_03_14_850Z-debug.log
2020-05-30T00:03:14.907689+00:00 heroku[web.1]: Process exited with status 1
2020-05-30T00:03:14.943718+00:00 heroku[web.1]: State changed from starting to crashed

这是我的 package.json

{
   "name": "discordtoornamentmanager",
   "version": "1.0.0",
   "description": "",
   "main": "dist/app.js",
   "type": "module",
   "scripts": {
      "test": "echo \"Error: no test specified\" && exit 1",
      "dev": "nodemon -x ts-node src/App.ts",
      "start": "ts-node src/App.ts"
   },
   "keywords": [],
   "author": "",
   "license": "ISC",
   "dependencies": {
      "@types/node": "^14.0.5",
      "axios": "^0.19.2",
      "discord.js": "^12.2.0",
      "pg": "^8.2.1",
      "reflect-metadata": "^0.1.10",
      "typeorm": "0.2.25",
      "typescript": "^3.9.3",
      "nodemon": "^2.0.4",
      "ts-node": "8.10.1"

   }
}

这是我的 tsconfig

{
   "compilerOptions": {
      "lib": [
         "es6"
      ],
      "target": "es6",
      "module": "commonjs",
      "moduleResolution": "node",
      "outDir": "dist",
      "resolveJsonModule": true,
      "emitDecoratorMetadata": true,
      "esModuleInterop": true,
      "experimentalDecorators": true,
      "sourceMap": true
   },
   "include": ["src/**/*.ts"],
   "exclude": ["node_modules", "**/*.spec.ts"]
}

Answer 1

在我看来，这个答案是最好的。/sf/answers/5222570951/

太棒了；经过多年的尝试ts-node，只需使用tsx开箱即用的产品即可。

npm i -D tsx
npx tsx src/index.ts

npm： https: //www.npmjs.com/package/tsx

• 截至撰写本文时，每周下载量已达到 40 万，并且还在不断上升。

Answer 2

2022 年 3 月

\n

使用：节点 16.6.2、ts-node v 10.7.0

\n

对我有用的是"type": "module"in package.json, 并添加

\n

node --experimental-specifier-resolution=node --loader ts-node/esm ./src/app.ts\n

\n

tsconfig.json：

\n

{\n    "compilerOptions": {\n      "module": "ESNext",\n      "esModuleInterop": true,\n      "target": "ESNext",\n      "moduleResolution": "Node",\n      "outDir": "dist",\n      "forceConsistentCasingInFileNames": true,\n      "noFallthroughCasesInSwitch": true,\n      "isolatedModules": false,\n      "strict": true,\n      "noImplicitAny": true,\n      "useUnknownInCatchVariables": false,\n      "inlineSourceMap": true\n    },\n    "ts-node": {\n        "esm": true\n    },\n    "lib": ["esnext"]\n}\n

\n

感谢 @FelipePlets在这里提供了有用的答案

\n

编辑\n您可能想要使用非选项esnext，根据ts 文档：

\n

\n

特殊的 ESNext 值指的是您的 TypeScript 版本支持的最高版本。应谨慎使用此设置，因为它在不同的 TypeScript 版本之间并不意味着相同的事情，并且可能会使升级变得更不可预测。

\n

\n

Answer 3

删除"type": "module"和package.json添加：

  "compilerOptions": {
    "module": "CommonJS"
  },

tsconfig.json为我解决了这个问题。

Answer 4

"type": "module"从 package.json 中删除

https://github.com/TypeStrong/ts-node/issues/935

如果您不想删除"type": "module"（例如，如果您import在 .ts 中使用允许从模块推断类型的语句），则可以在 中使用以下选项tsconfig.json：

{
  "compilerOptions": {
    "esModuleInterop": true,
  }
}

然后你可以使用配置启动服务器ts-node。

安装：

npm install -g ts-node

跑：

ts-node my_server.ts

Answer 5

解决方案一

1. "type": "module"如果已添加，请从 package.json 中删除
2. 在将模块属性设置为 CommonJStsconfig.json下，compilerOptionsmodule: "CommonJS"moduleResolution: "Node"

解决方案二

如果第一个不起作用，或者您出于某种原因必须保留module: "ESNext"

1-添加"type": "module"到package.json

2-安装 ts-nodenpm i -g ts-node

3- 转到tsconfig.json并添加以下内容：

{
    "compilerOptions": {
        "module": "ESNext",
        "moduleResolution": "Node",
        /* ... your props ... */
    },
    "ts-node": {
        "esm": true
    }
}

4- 运行ts-node fileName.ts

Answer 6

尝试将其添加到您的tsconfig.json

"ts-node": {
    "esm": true,
    "experimentalSpecifierResolution": "node",
}

我能够修复看起来tsconfig.json像这样的：

{
  "compilerOptions": {
    "target": "es2022",
    "lib": ["ES2022"],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noFallthroughCasesInSwitch": true,
    "module": "ES2022",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
  },
  "exclude": [
    "node_modules",
  ],
  "ts-node": {
    "esm": true,
    "experimentalSpecifierResolution": "node",
  }
}

Answer 7

用

node --loader ts-node/esm ./my-script.ts

代替

ts-node ./my-script.ts

Answer 8

我第一次遇到这个问题可能是一年多前，ts-node 尚未修复它。上述解决方案都不适合我，而且我似乎已经尝试了所有方法。

我只是求助于使用tsc --outDir out file.ts然后正常运行文件node out/file.js，然后添加out到.gitignore.

背后的想法ts-node很棒，但当它无法处理像这样看似简单的例子时，真的很糟糕。抱歉，该解决方案不使用 ts-node，但我无法让它工作。

Answer 9

我对 package.json 和 tsconfig.json 做了一些更改。最后，它对我有用！

1. 将 "type": "module" 添加到 package.json
2. 取消注释 tsconfig.json 中的 "moduleResolution": "node" 部分
3. 将 tsconfig.json 中的“module”部分更改为“ESNEXT”
4. 然后只需使用此节点运行主脚本 --loader ts-node/esm .\index.ts

tsconfig.json

{
"compilerOptions": {
/* Visit https://aka.ms/tsconfig.json to read more about this file */

/* Projects */
// "incremental": true,                              /* Enable incremental compilation */
// "composite": true,                                /* Enable constraints that allow a TypeScript project to be used with project references. */
// "tsBuildInfoFile": "./",                          /* Specify the folder for .tsbuildinfo incremental compilation files. */
// "disableSourceOfProjectReferenceRedirect": true,  /* Disable preferring source files instead of declaration files when referencing composite projects */
// "disableSolutionSearching": true,                 /* Opt a project out of multi-project reference checking when editing. */
// "disableReferencedProjectLoad": true,             /* Reduce the number of projects loaded automatically by TypeScript. */

/* Language and Environment */
"target": "es5",                                     /* Set the JavaScript language version for emitted JavaScript and include compatible library declarations. */
// "lib": [],                                        /* Specify a set of bundled library declaration files that describe the target runtime environment. */
// "jsx": "preserve",                                /* Specify what JSX code is generated. */
// "experimentalDecorators": true,                   /* Enable experimental support for TC39 stage 2 draft decorators. */
// "emitDecoratorMetadata": true,                    /* Emit design-type metadata for decorated declarations in source files. */
// "jsxFactory": "",                                 /* Specify the JSX factory function used when targeting React JSX emit, e.g. 'React.createElement' or 'h' */
// "jsxFragmentFactory": "",                         /* Specify the JSX Fragment reference used for fragments when targeting React JSX emit e.g. 'React.Fragment' or 'Fragment'. */
// "jsxImportSource": "",                            /* Specify module specifier used to import the JSX factory functions when using `jsx: react-jsx*`.` */
// "reactNamespace": "",                             /* Specify the object invoked for `createElement`. This only applies when targeting `react` JSX emit. */
// "noLib": true,                                    /* Disable including any library files, including the default lib.d.ts. */
// "useDefineForClassFields": true,                  /* Emit ECMAScript-standard-compliant class fields. */

/* Modules */
"module": "ESNEXT",  // ****HERE                          /* Specify what module code is generated. */
// "rootDir": "./",                                  /* Specify the root folder within your source files. */
"moduleResolution": "node",   // ****HERE                     /* Specify how TypeScript looks up a file from a given module specifier. */
// "baseUrl": "./",                                  /* Specify the base directory to resolve non-relative module names. */
// "paths": {},                                      /* Specify a set of entries that re-map imports to additional lookup locations. */
// "rootDirs": [],                                   /* Allow multiple folders to be treated as one when resolving modules. */
// "typeRoots": [],                                  /* Specify multiple folders that act like `./node_modules/@types`. */
// "types": [],                                      /* Specify type package names to be included without being referenced in a source file. */
// "allowUmdGlobalAccess": true,                     /* Allow accessing UMD globals from modules. */
// "resolveJsonModule": true,                        /* Enable importing .json files */
// "noResolve": true,                                /* Disallow `import`s, `require`s or `<reference>`s from expanding the number of files TypeScript should add to a project. */

/* JavaScript Support */
// "allowJs": true,                                  /* Allow JavaScript files to be a part of your program. Use the `checkJS` option to get errors from these files. */
// "checkJs": true,                                  /* Enable error reporting in type-checked JavaScript files. */
// "maxNodeModuleJsDepth": 1,                        /* Specify the maximum folder depth used for checking JavaScript files from `node_modules`. Only applicable with `allowJs`. */

/* Emit */
// "declaration": true,                              /* Generate .d.ts files from TypeScript and JavaScript files in your project. */
// "declarationMap": true,                           /* Create sourcemaps for d.ts files. */
// "emitDeclarationOnly": true,                      /* Only output d.ts files and not JavaScript files. */
// "sourceMap": true,                                /* Create source map files for emitted JavaScript files. */
// "outFile": "./",                                  /* Specify a file that bundles all outputs into one JavaScript file. If `declaration` is true, also designates a file that bundles all .d.ts output. */
// "outDir": "./",                                   /* Specify an output folder for all emitted files. */
// "removeComments": true,                           /* Disable emitting comments. */
// "noEmit": true,                                   /* Disable emitting files from a compilation. */
// "importHelpers": true,                            /* Allow importing helper functions from tslib once per project, instead of including them per-file. */
// "importsNotUsedAsValues": "remove",               /* Specify emit/checking behavior for imports that are only used for types */
// "downlevelIteration": true,                       /* Emit more compliant, but verbose and less performant JavaScript for iteration. */
// "sourceRoot": "",                                 /* Specify the root path for debuggers to find the reference source code. */
// "mapRoot": "",                                    /* Specify the location where debugger should locate map files instead of generated locations. */
// "inlineSourceMap": true,                          /* Include sourcemap files inside the emitted JavaScript. */
// "inlineSources": true,                            /* Include source code in the sourcemaps inside the emitted JavaScript. */
// "emitBOM": true,                                  /* Emit a UTF-8 Byte Order Mark (BOM) in the beginning of output files. */
// "newLine": "crlf",                                /* Set the newline character for emitting files. */
// "stripInternal": true,                            /* Disable emitting declarations that have `@internal` in their JSDoc comments. */
// "noEmitHelpers": true,                            /* Disable generating custom helper functions like `__extends` in compiled output. */
// "noEmitOnError": true,                            /* Disable emitting files if any type checking errors are reported. */
// "preserveConstEnums": true,                       /* Disable erasing `const enum` declarations in generated code. */
// "declarationDir": "./",                           /* Specify the output directory for generated declaration files. */

/* Interop Constraints */
// "isolatedModules": true,                          /* Ensure that each file can be safely transpiled without relying on other imports. */
// "allowSyntheticDefaultImports": true,             /* Allow 'import x from y' when a module doesn't have a default export. */
"esModuleInterop": true,                             /* Emit additional JavaScript to ease support for importing CommonJS modules. This enables `allowSyntheticDefaultImports` for type compatibility. */
// "preserveSymlinks": true,                         /* Disable resolving symlinks to their realpath. This correlates to the same flag in node. */
"forceConsistentCasingInFileNames": true,            /* Ensure that casing is correct in imports. */

/* Type Checking */
"strict": true,                                      /* Enable all strict type-checking options. */
// "noImplicitAny": true,                            /* Enable error reporting for expressions and declarations with an implied `any` type.. */
// "strictNullChecks": true,                         /* When type checking, take into account `null` and `undefined`. */
// "strictFunctionTypes": true,                      /* When assigning functions, check to ensure parameters and the return values are subtype-compatible. */
// "strictBindCallApply": true,                      /* Check that the arguments for `bind`, `call`, and `apply` methods match the original function. */
// "strictPropertyInitialization": true,             /* Check for class properties that are declared but not set in the constructor. */
// "noImplicitThis": true,                           /* Enable error reporting when `this` is given the type `any`. */
// "useUnknownInCatchVariables": true,               /* Type catch clause variables as 'unknown' instead of 'any'. */
// "alwaysStrict": true,                             /* Ensure 'use strict' is always emitted. */
// "noUnusedLocals": true,                           /* Enable error reporting when a local variables aren't read. */
// "noUnusedParameters": true,                       /* Raise an error when a function parameter isn't read */
// "exactOptionalPropertyTypes": true,               /* Interpret optional property types as written, rather than adding 'undefined'. */
// "noImplicitReturns": true,                        /* Enable error reporting for codepaths that do not explicitly return in a function. */
// "noFallthroughCasesInSwitch": true,               /* Enable error reporting for fallthrough cases in switch statements. */
// "noUncheckedIndexedAccess": true,                 /* Include 'undefined' in index signature results */
// "noImplicitOverride": true,                       /* Ensure overriding members in derived classes are marked with an override modifier. */
// "noPropertyAccessFromIndexSignature": true,       /* Enforces using indexed accessors for keys declared using an indexed type */
// "allowUnusedLabels": true,                        /* Disable error reporting for unused labels. */
// "allowUnreachableCode": true,                     /* Disable error reporting for unreachable code. */

/* Completeness */
// "skipDefaultLibCheck": true,                      /* Skip type checking .d.ts files that are included with TypeScript. */
"skipLibCheck": true                                 /* Skip type checking all .d.ts files. */
}}

包.json

{
"name": "async-with-ts",
"version": "1.0.0",
"main": "index.js",
"license": "MIT",
"type": "module", // ****HERE
"devDependencies": {
"@types/node-fetch": "^3.0.3",
"ts-node": "^10.2.1",
"typescript": "^4.4.2"
},
"dependencies": {
"node-fetch": "^3.0.0"
  }
}

您应该注意使用此命令

node --loader ts-node/esm .\index.ts

Answer 10

经过对ts-node / puppeteer配置的一些实验后，我想出了这个：

包.json

{
    "type": "module",
    "scripts": {
        "start": "npx ts-node main.ts"
    },
    ...
}

tsconfig.json

{
    "ts-node": { "esm": true, "experimentalSpecifierResolution": "node" },
    "compilerOptions": {
        "esModuleInterop": true,
        "moduleResolution": "node",
        "module": "ESNext",
        ...
    },
    ...
}

非常适合在 TypeScript 环境中运行 puppeteer。
（使用TypeScript 4.9.4和ts-node 10.9.1运行NodeJS 19.0.0）

Answer 11

我尝试通过以下方法消除此错误，但失败：(1)-使用.mts扩展。(2)- 使用type:commonjs而不是type:modulein package.json（这将not让你在你的 TS 文件中使用'import'，但是我想要这样，因此我认为这次尝试失败了）。(3)-Restarting的VS-Code

然后我尝试了以下操作并成功：(1)-在命令--esm中使用标志ts-node。例如=> npx ts-node --esm ./src/index.ts。(2) - 在里面，在' 右括号命名tsConfig.json后添加另一个选项，并将其选项设置为，如下所示：Compiler options"ts-node""esm""true"

{
  "compilerOptions": {
    "module": "ESNext",
    "moduleResolution": "Node",
    /* ... other props ... */
  },
  "ts-node": {
    "esm": true, /* ... Line to be added ... */
  } 
}

Answer 12

您可以使用ts-node-esm而不是ts-node，保留"type":"module"在 package.json 中，并import './module.js'在 .ts 文件中使用。

相关： https: //github.com/TypeStrong/ts-node/issues/1007

更新：

这个答案有一个更好的解决方案，允许导入没有 .js 扩展名的模块：

/sf/answers/4561416261/

Answer 13

跑步对我有用ts-node。--esm

例如：

ts-node --esm src/App.ts

该错误是由于尝试导入没有 ES Modules 标志的模块而导致的，该模块ts-node不支持。

Answer 14

这个bug还是比较有趣的。我发现它特定于 Node.js 版本 18。为了解决这个问题，我使用 NVM 降级到 Node.js 版本 16。令人惊讶的是，问题消失了，无需对我的代码或配置进行任何修改。对于那些在开发环境中使用 ts-node 和 nodemon 的人，我建议降级到 Node.js 版本 16，而不是使用版本 18。