Typescript 和 Node.js 错误“SyntaxError:无法在模块外使用导入语句”

Posted

技术标签:

【中文标题】Typescript 和 Node.js 错误“SyntaxError:无法在模块外使用导入语句”【英文标题】:Typescript and Node.js error "SyntaxError: Cannot use import statement outside a module" 【发布时间】:2021-10-06 22:20:58 【问题描述】:

运行 rpm run start 后,会打印错误:SyntaxError: Cannot use import statement outside a module。 注意:我将它与 GCP Cloud Run 一起使用。

package.json

 
  "name": "auth-api-public",
  "version": "0.0.1",
  "main": "src/index.ts",
  "type": "module",
  "scripts": 
    "start": "node src/index.ts",
    "lint": "eslint src/**.ts",
    "fix": "eslint --fix *.ts"
  ,
  "author": "Jacob Miller",
  "engines": 
    "node": ">=12.0.0"
  ,
  "dependencies": 
    "@google-cloud/secret-manager": "^3.9.0",
    "express": "^4.17.1",
    "firebase-admin": "^9.11.0",
    "stytch": "^3.0.2"
  ,
  "devDependencies": 
    "@typescript-eslint/eslint-plugin": "^3.9.1",
    "@typescript-eslint/parser": "^3.8.0",
    "eslint": "^7.30.0",
    "eslint-config-google": "^0.14.0",
    "eslint-config-prettier": "8.3.0",
    "eslint-plugin-import": "^2.23.4",
    "eslint-plugin-node": "11.1.0",
    "eslint-plugin-promise": "5.1.0"
  

然后我有一个名为 src 的文件夹,该文件夹包含 index.ts 中的导入语句(参见文件结构的屏幕截图)。

这是导入语句代码:

import * as express from "express";
import * as stytch from "stytch";
import * as admin from "firebase-admin";

这是 tsconfig.json:

    
  "compilerOptions": 
    "target": "es5",
    "module": "commonjs",
    "declaration": true,
    "outDir": "./dist",
    "strict": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true
  


    // 
    //   "compilerOptions": 
    //     "outDir": "./built",
    //     "allowJs": true,
    //     "target": "es6",
    //     "noImplicitReturns": true,
    //     "noUnusedLocals": true,
    //    "moduleResolution": "node",
    //     "sourceMap": true,
    //     "strict": false,
    //   ,
    //   "include": ["src"],
    //   "compileOnSave": true,
    // 

然后是运行 npm run start 后的错误信息截图:

【问题讨论】:

很难说,但至少我看到你在 devdep 中错过了 ts-node,npm i ts-node -D 还可以看看nestjs,它是一个具有打字稿功能的框架,我们通过nestjs开发了我们的应用程序并部署到云上运行 好的,我昨晚和早上一直在研究Nest,但有一个问题,云运行和云功能,是否需要任何配置?这就是我的意思:我运行命令来创建嵌套项目。我有巢猫模板。然后我想部署到云运行或功能。我需要配置什么才能让 GCP 与嵌套一起使用? whatdafox.com/deploy-nest-js-on-google-cloud-run @JacobMiller 发布了答案,有帮助吗? 【参考方案1】:

我希望全局安装 Typescript (npm i -g typescript)。除了安装 javascript npm,你还应该安装 Typescript 版本。下面是一个如何做到这一点的例子,npm install express @types/express 对所有存在 Typescript 版本的 npm 模块执行此操作。在此处分享 tsconfig.json 的配置。确保你在那里使用 commonjs。

检查以下配置是否适合您。


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

    /* Basic Options */
    // "incremental": true,                   /* Enable incremental compilation */
    "target": "es5",                          /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019', 'ES2020', or 'ESNEXT'. */
    "module": "commonjs",                     /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', 'es2020', or 'ESNext'. */
    // "lib": [],                             /* Specify library files to be included in the compilation. */
    // "allowJs": true,                       /* Allow javascript files to be compiled. */
    // "checkJs": true,                       /* Report errors in .js files. */
    // "jsx": "preserve",                     /* Specify JSX code generation: 'preserve', 'react-native', or 'react'. */
    "declaration": true,                   /* Generates corresponding '.d.ts' file. */
    // "declarationMap": true,                /* Generates a sourcemap for each corresponding '.d.ts' file. */
    // "sourceMap": true,                     /* Generates corresponding '.map' file. */
    // "outFile": "./",                       /* Concatenate and emit output to single file. */
    "outDir": "./dist",                        /* Redirect output structure to the directory. */
    // "rootDir": "./",                       /* Specify the root directory of input files. Use to control the output directory structure with --outDir. */
    // "composite": true,                     /* Enable project compilation */
    // "tsBuildInfoFile": "./",               /* Specify file to store incremental compilation information */
    // "removeComments": true,                /* Do not emit comments to output. */
    // "noEmit": true,                        /* Do not emit outputs. */
    // "importHelpers": true,                 /* Import emit helpers from 'tslib'. */
    // "downlevelIteration": true,            /* Provide full support for iterables in 'for-of', spread, and destructuring when targeting 'ES5' or 'ES3'. */
    // "isolatedModules": true,               /* Transpile each file as a separate module (similar to 'ts.transpileModule'). */

    /* Strict Type-Checking Options */
    "strict": true,                           /* Enable all strict type-checking options. */
    // "noImplicitAny": true,                 /* Raise error on expressions and declarations with an implied 'any' type. */
    // "strictNullChecks": true,              /* Enable strict null checks. */
    // "strictFunctionTypes": true,           /* Enable strict checking of function types. */
    // "strictBindCallApply": true,           /* Enable strict 'bind', 'call', and 'apply' methods on functions. */
    // "strictPropertyInitialization": true,  /* Enable strict checking of property initialization in classes. */
    // "noImplicitThis": true,                /* Raise error on 'this' expressions with an implied 'any' type. */
    // "alwaysStrict": true,                  /* Parse in strict mode and emit "use strict" for each source file. */

    /* Additional Checks */
    // "noUnusedLocals": true,                /* Report errors on unused locals. */
    // "noUnusedParameters": true,            /* Report errors on unused parameters. */
    // "noImplicitReturns": true,             /* Report error when not all code paths in function return a value. */
    // "noFallthroughCasesInSwitch": true,    /* Report errors for fallthrough cases in switch statement. */

    /* Module Resolution Options */
    // "moduleResolution": "node",            /* Specify module resolution strategy: 'node' (Node.js) or 'classic' (TypeScript pre-1.6). */
    // "baseUrl": "./",                       /* Base directory to resolve non-absolute module names. */
    // "paths": ,                           /* A series of entries which re-map imports to lookup locations relative to the 'baseUrl'. */
    // "rootDirs": [],                        /* List of root folders whose combined content represents the structure of the project at runtime. */
    // "typeRoots": [],                       /* List of folders to include type definitions from. */
    // "types": [],                           /* Type declaration files to be included in compilation. */
    // "allowSyntheticDefaultImports": true,  /* Allow default imports from modules with no default export. This does not affect code emit, just typechecking. */
    "esModuleInterop": true,                  /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
    // "preserveSymlinks": true,              /* Do not resolve the real path of symlinks. */
    // "allowUmdGlobalAccess": true,          /* Allow accessing UMD globals from modules. */

    /* Source Map Options */
    // "sourceRoot": "",                      /* Specify the location where debugger should locate TypeScript files instead of source locations. */
    // "mapRoot": "",                         /* Specify the location where debugger should locate map files instead of generated locations. */
    // "inlineSourceMap": true,               /* Emit a single file with source maps instead of having a separate file. */
    // "inlineSources": true,                 /* Emit the source alongside the sourcemaps within a single file; requires '--inlineSourceMap' or '--sourceMap' to be set. */

    /* Experimental Options */
    // "experimentalDecorators": true,        /* Enables experimental support for ES7 decorators. */
    // "emitDecoratorMetadata": true,         /* Enables experimental support for emitting type metadata for decorators. */

    /* Advanced Options */
    "skipLibCheck": true,                     /* Skip type checking of declaration files. */
    "forceConsistentCasingInFileNames": true  /* Disallow inconsistently-cased references to the same file. */
  
                                                                                                                 ```

【讨论】:

好的,这些 cmets 是我最初拥有的。我将 tsconfig 添加到问题中。不,此配置不起作用。 我也安装了类型包并卸载了原件,但这没有帮助。【参考方案2】:

您可以查看 *** 问题 1 和 2,其中 OP 遇到了类似的错误。 您也可以参考link1 和link2,其中已经提出并讨论了有关语法错误的类似问题:不能在模块外使用 import 语句。

确保您使用的是最新版本的 Nodejs,如果版本早于 13,那么您还必须在 package.json 文件中添加一个标志以及上述更改。

语法:

         node --experimental-modules program.js

【讨论】:

你可以在问题中清楚地看到他们使用了 "type"; “模块” @SamDean 你是对的……现在更新了。

以上是关于Typescript 和 Node.js 错误“SyntaxError:无法在模块外使用导入语句”的主要内容,如果未能解决你的问题,请参考以下文章

node.js/typescript 找不到本地模块

Node.js 的设计错误

@Types/node/index.d.ts TypeScript 错误 TS2309

向未来兼容——用ES2015+/TypeScript开发Node.js项目

Node.JS + TypeScript如何从堆栈跟踪中跟踪源代码?

在 TypeScript 文件中使用 node.d.ts 时出现编译错误