-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: ... #8900
Comments
Issue is related to is-promise and tracked here then/is-promise#14 |
I have the exact same problem and exact same environment. Please someone help! |
I have the same issue, i tried all possible ways all are throwing same error i have node (12.16.2), npm (6.14.4), yarn (1.21.1). |
Having the same issue as @sudir81 |
having the same issue |
Having the same issue |
having the same issue when run image in docker |
Workaround here: #8896 (comment) |
I've downgraded to node 12.11.1 and it works!! |
@RyanZim Works for me TKS! |
Same problem |
Downgrading fixed it!!! |
Same issue here. |
Solved!!! |
i have the same issue when generate new page in ionic 4 angular project |
Downgrade fix it! 1.- npm install -g n That was what I did! |
i too. |
Yeah, downgrade to 12.12.0 works! Thanks a lot... |
I had the same issue with quasar-cli, as I downgraded to 12.12.0 it worked, thanks. |
Simply running |
@sentisso tks, it's fixed for me
|
Duplicate of #8896, which should be resolved now. |
Downgrade @babel/runtime to 7.7.2 fixed it for me. |
Describe the bug
I'm trying to create a new React app using create-react-app and it in every way it just don't work. it throws the following error:
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: C:\Users\DevCarlosU\Desktop\test-final\node_modules\is-promise\index.js
Did you try recovering your dependencies?
No, it's for a new project.
Which terms did you search for in User Guide?
Environment
Environment Info:
current version of create-react-app: 3.4.1
running from C:\Users\DevCarlosU\AppData\Roaming\npm\node_modules\create-react-app
System:
OS: Windows 10 10.0.18362
CPU: (8) x64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
Binaries:
Node: 12.16.2 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.14.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.18362.449.0
Internet Explorer: 11.0.18362.1
npmPackages:
react: Not Found
react-dom: Not Found
react-scripts: Not Found
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce
(Write your steps here:)
Expected behavior
A new and clean React App project
Actual behavior
PS C:\Users\DevCarlosU\Desktop> npx create-react-app test
Creating a new React app in C:\Users\DevCarlosU\Desktop\test.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
added 1606 packages from 750 contributors and audited 931196 packages in 57.03s
58 packages are looking for funding
run
npm fund
for detailsfound 0 vulnerabilities
internal/modules/cjs/loader.js:1172
throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
^
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: C:\Users\DevCarlosU\Desktop\test\node_modules\is-promise\index.js
require() of ES modules is not supported.
require() of C:\Users\DevCarlosU\Desktop\test\node_modules\is-promise\index.js from C:\Users\DevCarlosU\Desktop\test\node_modules\run-async\index.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename C:\Users\DevCarlosU\Desktop\test\node_modules\is-promise\index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from C:\Users\DevCarlosU\Desktop\test\node_modules\is-promise\package.json.
code: 'ERR_REQUIRE_ESM'
}
Aborting installation.
node has failed.
Deleting generated file... node_modules
Deleting generated file... package.json
Done.
Reproducible demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
The text was updated successfully, but these errors were encountered: