-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[BUG] dash_mantine_components can't be found in dash 2.16.0 #2778
Comments
Hi @huong-li-nguyen this MRE works for me, can you test it in your environment?
requirements.txt
I'm going to test progressively adding the other libraries in your requirements.txt. |
Hey @celia-lm - thanks for your swift reply! It does work without any issues, so it must be something with our environment then 🤔 Thanks for checking though - much appreciated! We'll try to investigate on our side then. By any chance - do you have a clue from the error message what the potential issue could be? |
Could we get the full stacktrace from the browser. How is the first dmc component inserted in the layout? |
That seems to be the full trace:
The first mantine component is added like this - however, I think it's on our side as the below code works fine in a pure Dash app 🤔
|
I think this should be a MRE. Basically you need to use Dash pages to see the bug I think:
As you can see, it's not specific to dash mantine since the above uses |
Just checked and it got fixed with |
Describe your context
When running a dash app with the latest dash version, we're currently getting these console errors (see screenshot) and the app doesn't seem to render anymore.
Not sure if it's a bug on dash side or on the dash_mantine_library, so let me know if I should post the issue on the dash_mantine_library instead!
Thank you! Any help appreciated 🙏
Describe the bug
With the latest dash version our app seems to break. Seems like the dependencies can't be loaded in (see screenshot of the output)
Expected behavior
App running as normally (works with older dash versions)
Screenshots
Output when running the app in debug mode now:
The text was updated successfully, but these errors were encountered: