-
Notifications
You must be signed in to change notification settings - Fork 882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
React 19 Old Error Back: Uncaught Error: Map container is already initialized. #1133
Comments
I tried to upgrade a big app from react 18.3.0 to latest react 19 rc (19.0.0-rc-915b914b3a-20240515) and I'm facing the same issue. Here is the simplest repro : https://codesandbox.io/p/sandbox/thirsty-zeh-34ddlm Thanks for your help. |
The issue seems to go away by disabling Strict Mode. |
workaround: const isInitialized = useRef(false);
useEffect(() => {
isInitialized.current = true;
return () => {
isInitialized.current = false;
};
}, []);
if (!isInitialized) return null; |
I encountered the same issue while testing this in the Next.js v15 RC. The Map container fails to mount, even with dynamic loading. A temporary workaround as you mentioned is to disable reactStrictMode for the entire app by setting { reactStrictMode: false } in next.config. Hopefully, we can find a proper solution soon. __ Not sure what is causing the component to initialize twice, I may need to break out of react-leaflet. |
Disabling React Strict Mode to fix react-leaflet for now: PaulLeCam/react-leaflet#1133
Bug report in v4
Expected behavior
Working
Actual behavior
Well upgraded project to React 19 RC and the error popped up. Same as the past with ReactJs Upgrades
Not working getting error: Uncaught Error: Map container is already initialized.
Steps to reproduce
Upgrade project to React 19
The text was updated successfully, but these errors were encountered: