-
Notifications
You must be signed in to change notification settings - Fork 30
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
[Error] Ambiguous match found for serviceIdentifier: FlowRendererRegistry #42
Comments
For next js users i solved it using:
It seems that the inversify library used internally fails in the nextjs environment when executed twice. It would also be nice to find a comprehensive solution as this is a patch. |
It looks like the issue is caused by multiple instances. We'll fix it on our end as well. Thanks for the feedback! |
This is caused by the double rendering in React Strict Mode. In our underlying code, we have an implementation similar to the following:
As a result, we can see that Additionally, although React Strict Mode triggers repeated renders by default, the behavior is normal in the production environment. |
我也出现这个问题了。但是我没有使用next.js。我只是在vite创建的react ts项目中想要实现自由布局的基础用法,但是运行后出现错误 packages: 我注释掉了StrictMode就好了 |
strictMode 目前有问题,会导致 useMemo 失效 |
I'm trying to implement this product in a next js project, I follow the documentation https://flowgram.ai/en/examples/fixed-layout/fixed-layout-simple.html and I'm getting
Uncaught Error: Ambiguous match found for serviceIdentifier: FlowRendererRegistry
Is it a compatibility issue with next js? or is there something wrong with the library? I can't find a solution for the moment.
packages:
The text was updated successfully, but these errors were encountered: