Skip to content

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

Closed
wants to merge 1 commit into from
Closed

Conversation

archmoj
Copy link
Contributor

@archmoj archmoj commented Oct 5, 2021

Supersedes #3411
Addressing: plotly/plotly.js#5966
cc: @FernandezMathieu

@archmoj
Copy link
Contributor Author

archmoj commented Oct 5, 2021

Few tests are failing. I'll let @nicolaskruchten figure them out. Thanks!

@nicolaskruchten
Copy link
Contributor

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.

@FernandezMathieu
Copy link

Hi @nicolaskruchten , will you have time for this PR this week ?

@nicolaskruchten
Copy link
Contributor

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.

@nicolaskruchten
Copy link
Contributor

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?

@FernandezMathieu
Copy link

Hi @nicolaskruchten ,

I hear your difficulties with finding time to do this change.
But for companies like mine, using github sources is not compatible with security rules.
Maybe you can just release all dependencies that are uploaded on Github directly on NPM.

For your second message, we use jupyterlab 2, that not include pre-built extension installation.
We are working to upgrade our jupyterlab, meanwhile we are not able to rebuild our production environment.

Maybe we can install pre-built extension on Jupyterlab 2, let me know if i'm wrong here.

@nicolaskruchten
Copy link
Contributor

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?

@gvwilson
Copy link
Contributor

gvwilson commented Jun 6, 2024

@archmoj please let us know if this ought to be in Cycle 16

@gvwilson gvwilson added feature something new P2 considered for next cycle infrastructure build process etc. labels Aug 12, 2024
@gvwilson
Copy link
Contributor

@archmoj can we close this given your recent work? thanks - @gvwilson

@archmoj
Copy link
Contributor Author

archmoj commented Aug 23, 2024

It looks like plotly.py at the moment needs rebuild plot-schema.
So this require extra work.
Closing for now until but we may revisit this.

@archmoj archmoj closed this Aug 23, 2024
@archmoj archmoj deleted the use-plotly.js-dist branch August 23, 2024 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature something new infrastructure build process etc. P2 considered for next cycle
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants