Error importing formidable@3.2.4

[nsandeepn]

I get the below error when try to import formidable@3.2.4 in my project. Can you suggest a solution to resolve this.

-------<( "BABEL PARSING ERROR" )>------- Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: \node_modules\formidable\src\index.js
require() of ES modules is not supported.
require() of \node_modules\formidable\src\index.js from \app.router.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 index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from \node_modules\formidable\package.json.

at Module._extensions..js (internal/modules/cjs/loader.js:1089:13)
at Object.newLoader [as .js] (\node_modules\pirates\lib\index.js:141:7)
at Module.load (internal/modules/cjs/loader.js:937:32)
at Function.Module._load (internal/modules/cjs/loader.js:778:12)
at Module.require (internal/modules/cjs/loader.js:961:19)
at require (internal/modules/cjs/helpers.js:92:18)
at Object. (\app.router.js:2:1)
at Module._compile (internal/modules/cjs/loader.js:1072:14)
at Module._compile (\node_modules\pirates\lib\index.js:136:24)
at Module._extensions..js (internal/modules/cjs/loader.js:1101:10) {
code: 'ERR_REQUIRE_ESM'
}

[GrosSacASac]

Don't use babel, switch to import syntax

[Akxe]

It is not really possible for many people, including me, basically everyone that is using typescript to be exact.

[wbt]

You're using require() when you have to use import based on your project configuration.
See example usage code in the readme.

[Akxe]

The user can be importing the library but babel, webpack or many others will still use require. I think this library should be exporting 2 JS files, one for ES and one require. At least until this problem with all bundlers is resolved

[wbt]

I use webpack and import only and don't have a problem with webpack using require. Check your bundler configuration.

[Akxe]

Well... I use Angular and I do not have an option to change the bundler. Also, most packages do not support modules as of now. Thus exporting both types in these in-between times would be best.

[tunnckoCore]

@Akxe The user can be importing the library but babel, webpack or many others will still use require. I think this library should be exporting 2 JS files, one for ES and one require. At least until this problem with all bundlers is resolved

It does. We support both. The error is because messed up settings. Or maybe we didn't in the 3.2.4, but we does on the latest v3.