Webpack 5: configuration.node has an unknown property 'dgram'. These properties are valid:

I receive an error message:

Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.
 - configuration.node should be one of these:
   false | object { __dirname?, __filename?, global? }
   -> Include polyfills or mocks for various node stuff.
   Details:
    * configuration.node has an unknown property 'dgram'. These properties are valid:
      object { __dirname?, __filename?, global? }
      -> Options object for node compatibility features.
    * configuration.node has an unknown property 'fs'. These properties are valid:
      object { __dirname?, __filename?, global? }
      -> Options object for node compatibility features.
    * configuration.node has an unknown property 'net'. These properties are valid:
      object { __dirname?, __filename?, global? }
      -> Options object for node compatibility features.
    * configuration.node has an unknown property 'tls'. These properties are valid:
      object { __dirname?, __filename?, global? }
      -> Options object for node compatibility features.
    * configuration.node has an unknown property 'child_process'. These properties are valid:
      object { __dirname?, __filename?, global? }
      -> Options object for node compatibility features.

because of this setting:

node: {
    dgram: 'empty',
    fs: 'empty',
    net: 'empty',
    tls: 'empty',
    child_process: 'empty',
  },

What is the equavilent in Webpack 5?

Issue Analytics

State:
Created 3 years ago
Reactions:15
Comments:9 (1 by maintainers)

Top GitHub Comments

34reactions

alesrosinacommented, Feb 26, 2021

@slava-vishnyakov do you know how you would implement this solution for a rails webpacker.yml solution?

Inside config/webpack/*.js you should have some configs for your env (as described here: https://github.com/rails/webpacker#webpack-configuration). You need to remove those, so for example, i have in base.js:

const { environment } = require('@rails/webpacker')

const customConfig = {
  resolve: {
    fallback: {
      dgram: false,
      fs: false,
      net: false,
      tls: false,
      child_process: false
    }
  }
};

environment.config.delete('node.dgram')
environment.config.delete('node.fs')
environment.config.delete('node.net')
environment.config.delete('node.tls')
environment.config.delete('node.child_process')

environment.config.merge(customConfig);

module.exports = environment

it solved this issue for me

27reactions

Shigawirecommented, Feb 16, 2021

To anyone who also has the same problem: We’re using rails webpacker and had the described issue. Rails’ webpacker 5.x.x is only compatible with webpack 4.x.x (https://github.com/rails/webpacker/tree/5-x-stable). You might want to downgrade to webpack 4 😃