Frustrating warnings when used with webpack

[snario]

WARNING in ./~/harmony/~/formidable/lib/incoming_form.js
Critical dependencies:
1:43-50 require function is used in a way, in which dependencies cannot be statically extracted
 @ ./~/harmony/~/formidable/lib/incoming_form.js 1:43-50

WARNING in ./~/harmony/~/formidable/lib/incoming_form.js
Critical dependencies:
1:0-14 the request of a dependency is an expression
 @ ./~/harmony/~/formidable/lib/incoming_form.js 1:0-14

WARNING in ./~/harmony/~/formidable/lib/file.js
Critical dependencies:
1:43-50 require function is used in a way, in which dependencies cannot be statically extracted
 @ ./~/harmony/~/formidable/lib/file.js 1:43-50

WARNING in ./~/harmony/~/formidable/lib/file.js
Critical dependencies:
1:0-14 the request of a dependency is an expression
 @ ./~/harmony/~/formidable/lib/file.js 1:0-14

WARNING in ./~/harmony/~/formidable/lib/querystring_parser.js
Critical dependencies:
1:43-50 require function is used in a way, in which dependencies cannot be statically extracted
 @ ./~/harmony/~/formidable/lib/querystring_parser.js 1:43-50

WARNING in ./~/harmony/~/formidable/lib/querystring_parser.js
Critical dependencies:
1:0-14 the request of a dependency is an expression
 @ ./~/harmony/~/formidable/lib/querystring_parser.js 1:0-14

[tdeheurles]

Hi, Having same issue.

WARNING in ./~/restify/~/formidable/lib/incoming_form.js
Critical dependencies:
1:43-50 require function is used in a way in which dependencies cannot be statically extracted
 @ ./~/restify/~/formidable/lib/incoming_form.js 1:43-50

WARNING in ./~/restify/~/formidable/lib/file.js
Critical dependencies:
1:43-50 require function is used in a way in which dependencies cannot be statically extracted
 @ ./~/restify/~/formidable/lib/file.js 1:43-50

WARNING in ./~/restify/~/formidable/lib/json_parser.js
Critical dependencies:
1:43-50 require function is used in a way in which dependencies cannot be statically extracted
 @ ./~/restify/~/formidable/lib/json_parser.js 1:43-50

WARNING in ./~/restify/~/formidable/lib/querystring_parser.js
Critical dependencies:
1:43-50 require function is used in a way in which dependencies cannot be statically extracted
 @ ./~/restify/~/formidable/lib/querystring_parser.js 1:43-50

I'm importing restify that uses formidable.
Compiling with webpack generate an issue :

var crypto = require('crypto');
                     ^
TypeError: undefined is not a function

Does it tells something to someone ?
Running var crypto = require('crypto'); in my code does not generate that problem.

[tdeheurles]

For webpack user, adding :

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

fix the issue.

[quicksnap]

@tdeheurles Just wanted to say thank you for this. Ran into this when packaging for Electron--was very frustrating.

[quicksnap]

Looking at the webpack output, this issue could most likely be fixed by changing this line: https://github.com/felixge/node-formidable/blob/master/lib/incoming_form.js#L1
to something like this:

var require = require;
if (global.GENTLY) require = GENTLY.hijack(require);

Adding var require will prevent Webpack from shadowing the actual require with an empty var require; before the if (global.GENTLY).

Would a PR like that be accepted?

Duh.. that would break everything..

EDIT Clicked "Comment" too soon.

[davis]

this is still an issue

[gabrielstuff]

yup still be, and I confirm :

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

Fix it

[benjie]

Apologies for polluting the thread, but for anyone landing on this and still having issues afterwards who happens to be using superagent, note they have a wiki page saying what to do

[...] you can either use superagent's browser version directly (require('superagent/lib/client')), or fix your Webpack settings:

Add:

plugins.push(new webpack.DefinePlugin({ "global.GENTLY": false }));

and

node: {
  __dirname: true,
}

I also added the following, for good measure:

    alias: {
      'inherits': 'inherits/inherits_browser.js',
      'superagent': 'superagent/lib/client',
      'emitter': 'component-emitter',
    },

This cost me more time than I'd like to admit (oh look at that, it's just gone midnight), so posting here in the hopes it helps someone else since I landed on this page early on in my search...

[tunnckoCore]

Yea, that definitely a problem of how whole library is written. And kind of sucks. I believe we could change it and improve it for v2 release.

[isaachinman]

Just ran into this and lost an hour's time trying to figure it out!