Compile error the code inside var crypto = require('crypto'); TypeError: require is not a function

[WinterMain]

When I use formidable the complier prompt below error. After I removing using of formidable, it will run OK.

/Users/yanglidong/Documents/Work/Company/Git/YLD/samyoc/dist/server/server.js:254224
var crypto = require('crypto');
^

TypeError: require is not a function
at Object.map../file (/Users/yanglidong/Documents/Work/Company/Git/YLD/samyoc/dist/server/server.js:254224:15)

[tushar-singh]

I ran into the same issue with a library that has formidable as dependency.
I'm gonna assume you're using webpack to build it. In which case this is the fix

add this to webpack config:

externals: [
        {
            formidable: 'commonjs formidable',
        },
],

webpack will then skip over formidable and leave require('formdiable') intact – making node load it when you execute bundle, which seems to work

[raphaelsoul]

@tushar-singh not work with webpack4

[tunnckoCore]

@raphaelsoul, check migration guides.

Closing since it's not a problem here, but outside this lib and probably in the tooling. We working on improving docs and in near future it may be better.

@aiyld thanks for the report. If it is still a problem, feel free to open new issue.

Cheers.

[rw3iss]

Still an issue with webpack 4. Using externals entry doesn't work. Can't use the package.

[astonishqft]

I ran into the same issue with a library that has formidable as dependency.
I'm gonna assume you're using webpack to build it. In which case this is the fix

add this to webpack config:

externals: [
        {
            formidable: 'commonjs formidable',
        },
],

webpack will then skip over formidable and leave require('formdiable') intact – making node load it when you execute bundle, which seems to work

thanks! it works!

[im-danwu]

Hmm on webpack 4.29.6 and up and adding the externals works

[Diokuz]

2020, and the issue is still here :(

Have to additionally configure all my projects.

plugins: [
  new webpack.DefinePlugin({ 'global.GENTLY': false }),
],

Looks like it wont work after #539 ?

[tunnckoCore]

@Diokuz did you try canary dist-tag? Everything merged, fixed and introduced since 1.2.1 from before years, is in there. Codebase is refactored and gently is completely removed.

[Diokuz]

No, I didnt, because it is our subdependency. But the problem is still there in the latest version 1.2.2.

[tunnckoCore]

No, I didnt, because it is our subdependency.

Oh, I see. ;/

But the problem is still there in the latest version 1.2.2.

Yup. It was just a patch version to update the npm readme.

[markhughes]

Using 2.0.0-canary.20200504.1 resolved the issue on my end.. I don't think we have a choice but to use dev/canary builds at the moment. It looks like 2.0 has been in development for a few years, not sure if there is any news on a stable release?

For those wanting to do this for third party dependencies you can use npm shrinkwrap, and force your other dependencies to use it.