Victor Wu

https://github.com/web3/web3.js#troubleshooting-and-known-issues

https://stackoverflow.com/questions/64557638/how-to-polyfill-node-core-modules-in-webpack-5

Integrating wasm to webpack did not make any progress, showed same errors - https://www.npmjs.com/package/@rollup/plugin-wasm - recommended to have relative paths, using ./ instead of _dirname - add alias to file...

ordering of dependencies could cause issues, list parent dependencies below child dependencies

https://viglucci.io/how-to-polyfill-buffer-with-webpack-5

Rollup plugin for wasm https://www.npmjs.com/package/@rollup/plugin-wasm

building external wasm file https://stackoverflow.com/questions/60452332/rollup-bundling-embedding-wasm-code-from-an-external-module

https://github.com/localForage/localForage/wiki/Custom-Drivers https://github.com/vikrantpogula/localForage/commit/bdaf0059594bc3e61039726333982b4e6e690503

Yes we should remove it if we aren't using it. There were incompatibility and vulnerability issues. On Fri, Jun 17, 2022 at 4:37 PM Eric Martindale ***@***.***> wrote: > ***@***.****...