Omitting the process Webpack polyfill can cause issues

[ericsoco]

Fusion's Webpack config intentionally omits the process polyfill.

I'm filing this issue not to suggest specific action, but to highlight that this can cause difficult-to-debug issues with libraries that reference process directly in a way that is not e.g. compatible with EnvironmentPlugin (i.e. process.env checks).

Here's an example we ran into with react-markdown, which led us to vfile.

What does Fusion gain by not polyfilling process (which runs contrary to the default in Webpack and also Browserify), other than saving a few bytes in the bundle?

[rtsao]

FWIW webpack is removing default polyfilling.

Part of the reasoning was usage of Node built-ins usually indicates a situation where a Node.js dependency was erroneously being bundled. That said, I do think it would be better to include all polyfills by default, but issue warnings if they are ever used.

[ericsoco]

Probably worth adding the config to restore the webpack polyfill in a Fusion app here, for those who need it. Add the following to .fusionrc.js:

  nodeBuiltins: {
    process: true,
  },

[nsepehr]

@ericsoco thanks so much. I was having this issue and couldn't understand what's happening.

[ericsoco]

Here's another one I just came across, in this case requiring:

nodeBuiltins: {
  Buffer: true
}

I suppose the list may go on and on. I hope Webpack does a good job broadcasting the change to remove polyfilling as they roll out v5.

[akshaychauhan7737]

process is very much important object
facing this issue with request package which is highly used package.
request package is giving error when webpack is moved to webpack5

please either give a way to polyfil process in frontend applications.