-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Is react-dom/client required? #210
Comments
Hi, did you solve the issue? Check your import maps to ensure you are using the latest version of single-spa. |
@MilanKovacic I was unable to confirm that the reported change is still required. My related import maps are:
These are the only packages I have marked as external since they are the only ones I have full URLs for. I have not yet figured out how to import from a package. |
something similar happened to me but I corrected it by removing ^ from the react and react-dom dependencies. As they released that new version of react 18.3.0 is giving conflicts if it detects several versions of react. |
|
When I followed the single-spa-reactquick start instructions, it indicated that I should use
import ReactDOMClient from "react-dom/client";
instead ofimport ReactDOM from "react-dom";
. When I make the change, I get a run time error:application '@new/app' died in status SKIP_BECAUSE_BROKEN: m.createRoot is not a function
TypeError: application '@new/app' died in status SKIP_BECAUSE_BROKEN: m.createRoot is not a function
at exports.createRoot (https://localhost:8080/new-app.js:5404:16)
at u.elementToRender (https://localhost:8080/new-app.js:12748:5162)
at https://localhost:8080/new-app.js:12748:5262
at new Promise ()
at p (https://localhost:8080/new-app.js:12748:4017)
at https://cdn.jsdelivr.net/npm/single-spa@5.9.0/lib/system/single-spa.dev.js:303:33
The URL at the end seems strange, since all my package.json indicates that single-spa 6.0.1 should be used:
The new-app.tsx file which creates the error:
The only thing I can think of is that the singleSpaReact method was changed to get the client from ReactDOM...
I thought I should check here just in case.
The text was updated successfully, but these errors were encountered: