Frustrating warnings when used with webpack

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

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.

For webpack user, adding :

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

fix the issue.

@tdeheurles

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

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.

this is still an issue

yup still be, and I confirm :

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

Fix it

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...

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.

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

I have the same issue

@benjie

Hi @benjie, I'm using superagent and still getting the error after adding the config in the webpack.
I'm using webpack 2.4.1.

Here's my webpack.config snippets:

const plugins = [
    new webpack.DefinePlugin({ "global.GENTLY": false }),
    new webpack.IgnorePlugin(/\.(css|less)$/)
]


module.exports = {
    entry: handlers,
    output: {
        libraryTarget: 'commonjs',
        path: paths.appBuild,
        filename: '[name].js',
    },
    node: {
        __dirname: true,
    },
    externals: [
        'aws-sdk',
    ],
    resolve: {
        fallback: paths.nodePaths,
        extensions: ['.js', '.json', ''],
    },
    module: {
        preLoaders: preLoaders,
        loaders: loaders
    },
    plugins: plugins,
    target: 'node',
    devtool: 'source-map',
}

Warning Notification:

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

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

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

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

Error Message:

Type Error ---------------------------------------------

     require is not a function

@nazmy

@nazmy Sorry, can't help other than to suggest you try adding the aliases too?

Been dealing w/ this for a few hours & no luck w/ any of the existing solutions. The problem for me is a bit diff't though: I'm using an electron boilerplate with preconfig'd babel/webpack, and one of the plugins somewhere is doing something strange here.

Basically, babel/webpack/whatever sees this line:

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

And I guess considers require to need declaring, so it outputs it as:

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

This overwrites global.require & breaks everything else in the file.

Still trying to sort out which plugin is screwing it up, but unfortunately removing plugins one-by-one requires extensive fiddling w/ other things to make the project even start.

It seems like this one line is causing a lot of heartache, esp. since auth0 depends indirectly on this lib.

Does this line need to be required in exactly this way? If it's for testing, can't you set NODE_ENV='test' & wrap this?

@weaksou check the VERSION_NOTES file. In short, installing formidable as usual now installs the latest v2. The v3 is on v3 dist-tag npm install formidable@v3. The npm dist-tag will change soon too but that doesn't matter that much.

Too old. Closing.

For anyone else who is trying to investigate TypeError: hexoid is not a function and found out that this is the only thread in the entire Internet about the issue: downgrade your superagent (or similar library that uses formidable).

I went from 7 to 6 and that fixed the issue. Looking at the changelog, there's a formidable update mentioned.

For anyone else who is trying to investigate TypeError: hexoid is not a function and found out that this is the only thread in the entire Internet about the issue: downgrade your superagent (or similar library that uses formidable).

I went from 7 to 6 and that fixed the issue. Looking at the changelog, there's a formidable update mentioned.

I had to downgrade soap to version 0.43.0 to get this error to go away

I found another solution which doesn't require you to downgrade, but this only works if you're working with webpack. Add this to your webpack config file:

const { NormalModuleReplacementPlugin } = require('webpack');

module.exports = {
  ...
  plugins: [
    ...
    new NormalModuleReplacementPlugin(/^hexoid$/, require.resolve('hexoid/dist/index.js')),
  ]
}

I found another solution which doesn't require you to downgrade, but this only works if you're working with webpack. Add this to your webpack config file:
const { NormalModuleReplacementPlugin } = require('webpack');

module.exports = {
  ...
  plugins: [
    ...
    new NormalModuleReplacementPlugin(/^hexoid$/, require.resolve('hexoid/dist/index.js')),
  ]
}

This worked for Next JS :)

    if (!isServer) {
      config.resolve.fallback.fs = false
      config.resolve.fallback.dns = false
      config.resolve.fallback.net = false
    }

    config.plugins.push(
        new NormalModuleReplacementPlugin(/^hexoid$/, require.resolve('hexoid/dist/index.js')),
    );
    return config

downgrade superagent to v6.1.0 to resolve hexoid lib linking issue (#143

Having recently come across this same issue, I eventually discovered this fixed it

I tried build a clean new project only with express and formidable, it works. But when I build a electron project by Vue/Cli and Vue-electron try require formidable on main.js (or background.js ) it shows up this error:

App threw an error during load
TypeError: hexoid is not a function

Must be something wrong with webpack or vue or electrons build system.

And I find the solution, Add formidable to externals on vue.config.js under the electronBuilder option. Anyone try to use formidable at vue-electron project should try this.
// vue.config.js
module.exports = {
  pluginOptions: {
    electronBuilder: {
      // List native deps here if they don't work
      externals: ['formidable'],
    }
  }
}

webpack config also has externals prop, just mentioning

I found this issue while using webpack for a server application, I used webpack-node-externals as externals: [webpackNodeExternals()], docs here. This allows the bundle file to has node dependencies included.

For me the issue was the same, but in a different context, hope this help more than one.

For webpack user, adding :
plugins: [
     new webpack.DefinePlugin({ "global.GENTLY": false })
],
fix the issue.

thank you so much. I would've never found this by myself, Google/StackOF/GH_Copilot had no clue how to fix it. Only you did!

Navigation Menu

Repository navigation

Frustrating warnings when used with webpack #337

52 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Frustrating warnings when used with webpack #337

Description

Activity

tdeheurles commented on Nov 3, 2015

tdeheurles commented on Nov 3, 2015

quicksnap commented on Dec 7, 2015

quicksnap commented on Dec 8, 2015

davis commented on Feb 10, 2016

gabrielstuff commented on Feb 12, 2016

benjie commented on Dec 2, 2016

tunnckoCore commented on Jan 16, 2017

isaachinman commented on Apr 7, 2017

joseSantacruz commented on Apr 15, 2017

nazmy commented on Apr 21, 2017

benjie commented on Apr 21, 2017

brandonmp commented on May 3, 2017

52 remaining items

tunnckoCore commented on Nov 23, 2021

tunnckoCore commented on Apr 3, 2022

ahoys commented on May 5, 2022

jjmerri commented on Jun 29, 2022

dhruvit-r commented on Jul 30, 2022

skaraudio commented on Sep 22, 2022

Josh-a-e commented on Mar 13, 2023

PSoltes commented on Mar 13, 2023

ca-santiago commented on Apr 9, 2023

oyatek commented on May 13, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions