Integration module federation with ReactJS about automerge-classic HOT 6 CLOSED

Unfortunately I have no experience with webpack module federation. If I had to guess I would say this is probably something to do with the interaction between webpack experimental webassembly module support and whatever module federation is, but I can't offer you much help there - you'll probably need to dig into it a bit yourself. Maybe try reproducing this with a minimal webassembly dependency to check if it's automerge specific or just a general problem with webassembly dependencies?

from automerge-classic.

It looks like this app was created with create-react-app, which has some issues using webassembly. If you take a look at the "create react app" tab of https://automerge.org/docs/quickstart/ you can see one way to fix this, alternatively take a look at the javascript/examples/create-react-app demo at https://github.com/automerge/automerge-rs/tree/main/javascript/examples/create-react-app (note, not in this repo).

from automerge-classic.

I made it work using CRA as described in the docs. But the issue is when I try to use Module Federation, using the 1.0.1-preview.7 works fine... while the 2.0 break it.

from automerge-classic.

Have you tried using webpack directly rather than create-react-app? In my experience create-react-app is extremely buggy when it comes to webassembly bundling.

from automerge-classic.

yes, the sample app (folder create-project-mf) is using automerge + webpack (not CRA), but when integrating with MF, it breaks, and using older version of automerge works fine.

from automerge-classic.

I found the issue, there are two things that fixed using Automerge as Module Federation. React.lazy and Suspense

from automerge-classic.