我一直想把它修好。以下是有效的方法:

使用最新的节点版本。我使用的是v14.15.5。运行:node——version来验证你的版本 命名文件，使它们都以.mjs而不是.js结尾

例子:

mod.mjs

export const STR = 'Hello World'

test.mjs

import {STR} from './mod.mjs'
console.log(STR)

执行命令node test.mjs

你应该看到“Hello World”。

不幸的是，Node.js还不支持ES6的导入。

要完成您要做的事情(导入Express模块)，这段代码应该足够了

var express = require("express");

另外，确保通过运行安装了Express

$ npm install express

有关学习Node.js的更多信息，请参阅Node.js文档。

从版本14开始，Node的稳定版本支持import语句。x LTS。

你所需要做的就是在package.json中指定"type": "module"。

My project uses node v10.21.0, which still does not support ES6 import keyword. There are multiple ways to make node recognize import, one of them is to start node with node --experimental-modules index.mjs (The mjs extension is already covered in one of the answers here). But, this way, you will not be able to use node specific keyword like require in your code. If there is need to use both nodejs's require keyword along with ES6's import, then the way out is to use the esm npm package. After adding esm package as a dependency, node needs to be started with a special configuration like: node -r esm index.js

我很惊讶esm竟然没有被提到。这个小但功能强大的包允许您使用import或require。

在项目中安装esm

$ NPM install——保存esm

更新您的节点启动脚本以使用esm

Node -r esm app.js

Esm就是管用。我在.mjs和——experimental-modules上浪费了大量的时间，却发现.mjs文件不能导入使用require或module.exports的文件。这是一个大问题，而esm允许你混合和匹配，它只是解决它…Esm就是管用。

作为Node.js v12(这可能是相当稳定的现在，但仍然标记为“实验”)，你有两个选项使用ESM (ECMAScript模块)在Node.js(文件，有第三种方法计算字符串)，以下是文档所说的:

The --experimental-modules flag can be used to enable support for ECMAScript modules (ES modules). Once enabled, Node.js will treat the following as ES modules when passed to node as the initial input, or when referenced by import statements within ES module code: Files ending in .mjs. Files ending in .js, or extensionless files, when the nearest parent package.json file contains a top-level field "type" with a value of "module". Strings passed in as an argument to --eval or --print, or piped to node via STDIN, with the flag --input-type=module. Node.js will treat as CommonJS all other forms of input, such as .js files where the nearest parent package.json file contains no top-level "type" field, or string input without the flag --input-type. This behavior is to preserve backward compatibility. However, now that Node.js supports both CommonJS and ES modules, it is best to be explicit whenever possible. Node.js will treat the following as CommonJS when passed to node as the initial input, or when referenced by import statements within ES module code: Files ending in .cjs. Files ending in .js, or extensionless files, when the nearest parent package.json file contains a top-level field "type" with a value of "commonjs". Strings passed in as an argument to --eval or --print, or piped to node via STDIN, with the flag --input-type=commonjs.