It’s a bit hard to tell, but there may be more information in the browser console (usually shown by pressing F12).
My hunch is you’ve gotten the state of your frontend versions confused, which can be listed out via jupyter labextension list. The jupyterlab assets are distributed in jupyterlab-widgets:
Sometimes in-the-wild packages don’t have enough knowledge of the future to know they need to be up or downgraded when pre-release packages are in the mix.
what is the magic incantation to fix the setup?
Similarly, without the output of pip freeze, it’s hard to know exactly what the setup is.
I have found pip, in particular, to be kind of unpredictable when used interactively over a long period of time… I can’t recommend enough adopting something that gives you disposable, reproducible environments, e.g. tox, virtualenv, conda. This will allow you to more easily switch between multiple versions of upstreams, especially when using pre-release software… but really, whenever. Having one or more requirements.txt or environment.yml understood by multiple tools can also make this useful in e.g. CI… i’ve found some tools, such as poetry, to actively make this harder as it strives very hard for some kind of “right” answer, which is often not as useful as “likely to be found by a user.”
I am trying to use ipyaggrid at jupyterlab3.x recently. I have the same problem.‘Error displaying widget: model not found’. I tryed in jupyterlab2.x. It works.
Does anyone knows how to fixed this problem.It will be very thanks.
In addition,I tryed use ipyaggrid in jupyter notebook. It also useable.
Oh my God,I’m going nuts
help me please