-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
use plotly.js-dist instead of plotly.js #3412
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
Conversation
Few tests are failing. I'll let @nicolaskruchten figure them out. Thanks! |
This approach won't work... the overall code-gen system needs the full build. I can look into this next week or the week after. |
Hi @nicolaskruchten , will you have time for this PR this week ? |
I think someone will need to do some deeper engineering here to get the codegen system working with this dependency, or we will have to fix the underlying Plotly.js issue, because we can't merge this PR as-is, and no one on our team is available to dig into the needed work to build the extension using the dist bundle while running the codegen with the full bundle. |
I'm curious about why you need to build the extension locally as opposed to downloading it from NPM or just letting the plotly.py installation process handle loading the extension? |
Hi @nicolaskruchten , I hear your difficulties with finding time to do this change. For your second message, we use jupyterlab 2, that not include pre-built extension installation. Maybe we can install pre-built extension on Jupyterlab 2, let me know if i'm wrong here. |
So Plotly.js 2.6 is now out and should be buildable again without needing to connect to Github... Could you please see if your issue is resolved? |
@archmoj please let us know if this ought to be in Cycle 16 |
It looks like plotly.py at the moment needs rebuild plot-schema. |
Supersedes #3411
Addressing: plotly/plotly.js#5966
cc: @FernandezMathieu