Making js-ipfs supports webpack5

[FledgeXu]

• Version:
  "ipfs": "0.53.2",
• Platform:
  Darwin FledgeXus-MBP 20.2.0 Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64 x86_64

Severity:

Hight: Making JS-ipfs supports webpack5

Description:

Webpack5 removes Node.js core modules polyfills and it makes that js-ipfs can not just work in browser. How will the IPFS support webpack5?

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[achingbrain]

We've removed node globals from all the repos in the ipfs/ipld/multiformats orgs. There are still a few dependencies of IPFS that do things like reference process or Buffer without requireing them first, those will take longer to fix.

If you would like to help you can PR those repos to remove the use of node globals. I did cbor earlier today. I think some of the level repos need PRs, as does node-forge and some of the crypto libraries.

Otherwise the only solution is to stick to webpack 4 for now, or use a different bundler.

[Gozala]

We actually have one example that uses webpack5,
https://github.com/ipfs/js-ipfs/blob/master/examples/browser-service-worker/webpack.config.js