I'm making a discord bot in TypeScript using discord.js. When I tried to compile code this morning I got this error:
C:\SECRET\Kostegator\dist\Util\getMeme.js:17
const node_fetch_1 = __importDefault(require("node-fetch"));
^
Error [ERR_REQUIRE_ESM]: require() of ES Module C:\SECRET\Kostegator\node_modules\node-fetch\src\index.js from C:\SECRET\Kostegator\dist\Util\getMeme.js not supported.
Instead change the require of index.js in C:\SECRET\Kostegator\dist\Util\getMeme.js to a dynamic import() which is available in all CommonJS modules.
at Object.<anonymous> (C:\SECRET\Kostegator\dist\Util\getMeme.js:17:38)
at Object.<anonymous> (C:\SECRET\Kostegator\dist\Util\index.js:15:14)
at Object.<anonymous> (C:\SECRET\Kostegator\dist\Commands\BotOwner\startAutoUpdate.js:4:16)
at C:\SECRET\Kostegator\dist\Client\index.js:61:41
at Array.forEach (<anonymous>)
at ExtendedClient.<anonymous> (C:\SECRET\Kostegator\dist\Client\index.js:58:48)
at Generator.next (<anonymous>)
at C:\SECRET\Kostegator\dist\Client\index.js:27:71
at new Promise (<anonymous>)
at __awaiter (C:\SECRET\Kostegator\dist\Client\index.js:23:12)
at ExtendedClient.init (C:\SECRET\Kostegator\dist\Client\index.js:51:16)
at Object.<anonymous> (C:\SECRET\Kostegator\dist\index.js:19:4) {
code: 'ERR_REQUIRE_ESM'
}
Here's the GitHub repo: Kostegator
The current version of node-fetch is ONLY compatible with an ESM import (using import), not from CommonJS modules using require().
You have these choices to fix:
Switch your project to an ESM module and load it with import fetch from 'node-fetch';.
In a very recent version of nodejs, you can dynamically import an ESM module into a CommonJS module using let fetch = await import('node-fetch').
Use the v2 version of node-fetch that still supports being loaded with require() as explained here in the doc.
With the latest update, node-fetch only works by using import
You could just install the older version of it by
npm i node-fetch#2.6.1
For those coming here trying to deploy a NodeJS App using the cPanel feature, remember that under the hood it uses Phusion Passenger. This tool needs to have a non-module entry point like:
// entry.cjs DONT FORGET TO USE .cjs and not .js
async function loadApp() {
const { app } = await import("./app.js"); // this is your normal entry file - (index.js, main.js, app.mjs etc.)
}
loadApp()
The original answer is here (it deserves your vote): https://stackoverflow.com/a/71901828/14515077
Related
I am trying to create a standalone node.js project. The steps I followed are -
Created a new directory and initialised it with npm init.
Installed the new module for node-fetch.
Trying to import the fetch module using const fetch = require("node-fetch"); statement.
Getting the following error -
const fetch = require("node-fetch");
Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/jatin/Desktop/test-app/node_modules/node-fetch/src/index.js from /Users/jatin/Desktop/test-app/index.js not supported. Instead change the require of /Users/jatin/Desktop/test-app/node_modules/node-fetch/src/index.js in /Users/jatin/Desktop/test-app/index.js to a dynamic import() which is available in all CommonJS modules. at Object.<anonymous> (/Users/jatin/Desktop/test-app/index.js:2:15) { code: 'ERR_REQUIRE_ESM' }
The node version I have on my machine is - v16.9.0.
You should use an ES module import instead of require.
import * as fetch from 'node-fetch';
You could also use a dynamic import, as the error message states.
const fetch = import('node-fetch');
I want to use import in my nodejs project instead of using require.
So, I added,
"type": "module"
in my package.json.
import index from './index.js';
in server.js
when I run
node server.js
Error says,
internal/modules/cjs/loader.js:1174
throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
^
throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
^
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: ....
server.conf.js is pasted below.
import express from 'express';
import http from 'http';
let app = express();
let server = http.createServer(app);
import morgan from 'morgan';
import methodOverride from 'method-override';;
import path from 'path';
let port = process.env.PORT || 4000;
app.use(morgan('dev'));
app.use(methodOverride('X-HTTP-Method-Override'));
let router = express.Router();
import routes from '../app/routes';
routes(app, router, client);
server.listen(port);
console.log(`Wizardry is afoot on port ${port}`);
export {
app,
client
};
For my case I downgrade:
node-fetch ^3.0.0 → ^2.6.1
Problem solved.
According to stack-trace before you edit (https://stackoverflow.com/revisions/61558835/1):
internal/modules/cjs/loader.js:1174
throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
^
throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
^
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: H:\WORKSPACE\CMDs\node-basic\server.conf.js
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1174:13)
at Module.load (internal/modules/cjs/loader.js:1002:32)
at Function.Module._load (internal/modules/cjs/loader.js:901:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
at internal/main/run_main_module.js:18:47 {
code: 'ERR_REQUIRE_ESM'
}
I tried to locate the Node src who throws this error:
https://github.com/nodejs/node/blob/c24b74a7abec0848484671771d250cfd961f128e/lib/internal/modules/cjs/loader.js#L1234
// Native extension for .js
Module._extensions['.js'] = function(module, filename) {
if (filename.endsWith('.js')) {
const pkg = readPackageScope(filename);
// Function require shouldn't be used in ES modules.
if (pkg && pkg.data && pkg.data.type === 'module') {
// ...
throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
}
}
// ...
};
The comment Function require shouldn't be used in ES modules tells the js file to be loaded is an ES module, but the caller is trying to use require() function to load it.
Moreover, a double-check into Node src https://github.com/nodejs/node/blob/6cc94b2d7f69f1f541f7c5de3cb86e569fbd4aa3/lib/internal/errors.js#L1319 proves that H:\WORKSPACE\CMDs\node-basic\server.conf.js is the ES module to be loaded.
So I'm trying to guess who is trying to load server.conf.js in your app but no luck. Most likely there is a require('./server.conf.js') in your index.js or somewhere else. If you find it just change it into import to fix.
Had the same issue. I installed the latest node version and then it worked. Try the same. Also if you are using windows make sure it is the correct version i.e 64-bit, 32-bit.
in my case i had a data file (data.js) with products listed as objects inside an array. looked like this :
const data={
products:[
{
brand:'nike',
price:1200
},
{
brand:'adidas',
price:1400
}
]
}
export default data
THE ERROR was caused because i FOOLISHLY exported it like it was a function or class
and wrote:
export default data={
etc...
}
i DOUBT this is a case of your error BUT it shows nonetheless how cumbersome and often this error can show up. if its any clarity what im trying to say im basically saying that this usually shows up due to a file itself being unreadable from import. if you put "type": "module" then it is def a version of node, OR a problem on a base level with something you are trying to import. try deleting each of the imports one by one initially to see which one may be the cause. then work from there
Nothing fancy needed. Just update the Node.js version.
Check your NodeJS version for module compatibility("type": "module"), there are known issues on certain versions.
Most likely there is a require('./server.conf.js') in your index.js/server.js or in the dependent packages you are importing or somewhere else. If you find it just change it into import to fix.
1- Check you're all require statements
2- analyze dependent packages for a require statement in that code
Try a build ...
Try to deploy to NodeJS containers on GC, DO, AWS or HKU
I was also facing similar issue.
So I downgrade chalk module version from 5.0.1 to 4.1.0.
It worked for me.
In my case I was running Angular 13.X och Nx 14.X but my Node version was still 12.X so upgrading the Node version to ^14 solves the problem.
I updated the terminal node version to 16, deleted node_modules and installed it again. And fixed.
I'm trying to use exports and import on Node.js application, So I used the Node.js documentation ECMAScript Modules. But I am getting error
I am using,
v11.9.0
Run command node --experimental-modules app.js
How can I use ES6 export and import in Node.JS ? Preferred me the way that not using any additional package !
Code :
// test.js
module.exports = { one: 1 };
// app.js
import foo from './test.js';
console.log(foo);
Error :
(node:9352) ExperimentalWarning: The ESM module loader is experimental.
/home/Workspace/test/app.js:1
(function (exports, require, module, __filename, __dirname) { import foo from './test.js';
^^^
SyntaxError: Unexpected identifier
at new Script (vm.js:84:7)
at createScript (vm.js:264:10)
at Proxy.runInThisContext (vm.js:312:10)
at Module._compile (internal/modules/cjs/loader.js:694:28)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:745:10)
at Module.load (internal/modules/cjs/loader.js:626:32)
at tryModuleLoad (internal/modules/cjs/loader.js:566:12)
at Function.Module._load (internal/modules/cjs/loader.js:558:3)
at createDynamicModule (internal/modules/esm/translators.js:73:15)
at Object.meta.done (internal/modules/esm/create_dynamic_module.js:40:9)
As the doc says your files need a .mjs extension:
The --experimental-modules flag can be used to enable features for
loading ESM modules.
Once this has been set, files ending with .mjs will be able to be
loaded as ES Modules.
You have to currently use the flag and there is no "seamless" way to use them at the moment other than using a transpiler like babel.
As Quentin says CommonJS files can still use .js extension (you can mix and match).
I'm fairly new to nodejs. With the evolution of nodejs ( I have just installed v.10 ) what is the current simplest way to use ES6 features ( import statements etc ) in a new nodejs project - that "just works" . I want the least dependencies and the method with the fastest path to "just works".
I am finding the posts on the web a bit confusing.
Babel was installed previously for this sort of thing I understand
Node 10 Says ( Here ) enable using node --experimental-modules my-app.mjs
This post seems quite authoritative , but I think it's about creating packages more than using the syntax.
Please help! I seem to get the following errors for;
import {MagentoAccountApi} from 'js-magento-client';
Error 1:
SyntaxError: Unexpected token {
at new Script (vm.js:74:7)
at createScript (vm.js:246:10)
at Object.runInThisContext (vm.js:298:10)
at Module._compile (internal/modules/cjs/loader.js:646:28)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:689:10)
at Module.load (internal/modules/cjs/loader.js:589:32)
at tryModuleLoad (internal/modules/cjs/loader.js:528:12)
at Function.Module._load (internal/modules/cjs/loader.js:520:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:719:10)
at startup (internal/bootstrap/node.js:228:19)
If I try renaming the file to have an extension .mjs and load using: node --experimental-modules .\mtest.mjs , then I get this error:
(node:20224) ExperimentalWarning: The ESM module loader is experimental.
file:///F:/node/magento-test/mtest.mjs:1
import {MagentoAccountApi} from 'js-magento-client';
^^^^^^^^^^^^^^^^^
SyntaxError: The requested module 'js-magento-client' does not provide an export named 'MagentoAccountApi'
at ModuleJob._instantiate (internal/modules/esm/module_job.js:89:21)
I don't know if that is a packagage error , or a setup error.
Maybe Babel is still the right / easiest way to make this work..? I guess I don't want to start using something the is going to be deprecated soon.
At present, with the experimental loader, CommonJS interoperability only allows for a single default export. You can't use named exports with existing CommonJS modules, so currently you have to do this:
import Magneto from "js-magento-client";
const { MagentoAccountApi } = Magneto;
Which is not correct, but is in the process of being fixed apparently.
From the NodeJS v10 docs:
When loaded via import these modules will provide a single default
export representing the value of module.exports at the time they
finished evaluating.
import fs from 'fs';
fs.readFile('./foo.txt', (err, body) => {
if (err) {
console.error(err);
} else {
console.log(body);
}
});
All the comments above telling you that it's a bad idea to start out with an experimental feature are 100% on-point. The above is a good example. At some point this is going to change and you'll have to change your code. If you used Babel instead, you wouldn't have this issue.
End Goal:
To create Azure Function running Botframework-DirectlineJS with binding to Bot (Framework) using DirectLine secret.
Issue:
The above mentioned Botframework-DirectlineJS uses ES6 export and Azure Functions support Node 6.5.0 max doc. Hence the question how to import successfully the DirectlineJS in the index.js file of Azure function?
Error
```
2017-05-23T07:17:45.939 Exception while executing function: Functions.adapter. mscorlib: D:\home\site\wwwroot\adapter\importexportwrapper.js:1
(function (exports, require, module, __filename, __dirname) { import { DirectLine } from 'botframework-directlinejs';
^^^^^^
SyntaxError: Unexpected token import
at Object.exports.runInThisContext (vm.js:76:16)
at Module._compile (module.js:528:28)
at Object.Module._extensions.(anonymous function) [as .js] (D:\home\site\wwwroot\node_modules\node-hook\index.js:73:14)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object.<anonymous> (D:\home\site\wwwroot\adapter\index.js:4:2)
at Module._compile (module.js:556:32).
```
Currently the error was while trying to use npm import-export
Files
index.js
require('import-export');
require ('./importexportwrapper');
let directLine = new DirectLine({
secret: 'DirectlineSecretValue-here'
}
);```
importexportwrapper.js
import { DirectLine } from 'botframework-directlinejs';
Unfortunately it seems like import-export or node-hook doesn't play well with functions / edgejs (the environment we use to run node).
A couple options to try:
use babel to transpile es6 to es5 as a part of your deployment process.
write your function in typescript (index.ts) which will do import transpilation automatically - though this may fail for module dependencies, I haven't tried it out
You have three options: 1) Write your code using ES5, 2) setup a task runner (gulp/grunt/npm scripts) to convert your ES6+ code to ES5 using Babel, or 3) write your code in Typescript and compile it to ES5 via task runner/npm scripts.
The most straight-forward method would be: in your file importexportwrapper.js use require instead of import.
Example:
var directline = require('botframework-directlinejs');
Babel + Gulp Option
Install: npm install --save-dev gulp gulp-babel
Run:
var gulp = require("gulp");
var babel = require("gulp-babel");
gulp.task("default", function () {
return gulp.src("src/app.js") // your source files
.pipe(babel())
.pipe(gulp.dest("dist")); // your compiled output directory
});
Read more about Azure Functions Node.js versions here.