-
Notifications
You must be signed in to change notification settings - Fork 365
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
Uncaught Error: Script error for "@jupyter-widgets/base" #76
Comments
maybe not jason says:
|
The switch from jupyter-js-widgets to For the jupyter.org webpage, it's also hardcoded at ipywidgets 6: https://github.com/jupyter/jupyter.github.io/blob/fae454d82f28cf98ce0d1cc4cd1eec59a4a3fe45/widgets.html#L8. However, the code tries to load the ipywidgets 7 version of ipyleaflet. The quick fix is to only load the ipywidgets 6 version of ipyleaflet. The more permanent fix is to upgrade the website code to use ipywidgets 7. |
On second thought, it may not be that easy - I think loading the latest version is hardcoded in that embedding javascript. It's probably best to switch it to use ipywidgets 7, using instructions at http://ipywidgets.readthedocs.io/en/stable/migration_guides.html#updating-embedded-widgets and updating the json data file with a version from the latest ipywidgets release. |
Regardless, though, this is an issue with the Jupyter web page, not ipyleaflet, so I'll open an issue there. |
I opened jupyter/jupyter.github.io#240 to track the update to the webpage. With those two issues tracking these things, I'll close this one. |
The embedded version of ipyleaflet is broken. It does not work in nbviewer and in the
http://jupyter.org/widgets.html
It throws the:
Uncaught Error: Script error for "@jupyter-widgets/base", needed by: https://unpkg.com/jupyter-leaflet@*/dist/index.js
.the problem is the
module_name
that is resolved to@jupyter-widgets/base
instead of thejupyter-js-widgets
as the ipywidgets are available under thejupyter-js-widgets
name by requirejs onnbviewer
andhttp://jupyter.org/widgets.html
The text was updated successfully, but these errors were encountered: