Webpack >= 5 no longer include polyfills for node.js core modules by default.

[jamacku]

Module not found: Error: Can't resolve 'stream' in '/home/runner/work/ciboard/ciboard/node_modules/sax/lib'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
	- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "stream": false }

Possible solution: Install polyfills and resolve them or turn them off using new Webpack API

Blocks: #6

[mgrabovsky]

Looking closer at this: Specifying/overriding resolves requires changing the webpack config which is not possible with vanilla Create React App unless we eject. An alternative is to go the react-rewire-app way, which sort of monkey-patches the config at build time.

[mgrabovsky]

@Andrei-Stepanov Do you have a preferred way of solving this (eject vs. react-rewire-app)? We should fix this one day so that xml2js keeps working correctly.

[Andrei-Stepanov]

Hm, is only us who bumps into this? maybe try look for more solutions? I am against for 100% for eject. This is development code. I propose to google other solutions or practices that allows publish code on github.

[mgrabovsky]

Well, react-rewire-app seems to be a popular option for those who don't want to eject.

Another option that comes to mind is migrating to a different XML parsing library. The one we use was last updated 6 years ago, so the migration would be a prudent decision either way.

A quick search turns up two fair-looking candidates: htmlparser2 (~22 million weekly downloads, written in TypeScript) and fast-xml-parser (~4 million, JS but with TS declarations built in).