Plotly ESM broken on jsdelivr

[duaneatat]

The current version of plotly is broken on jsdelivr +esm

• https://cdn.jsdelivr.net/npm/plotly.js-dist-min@2.35.2/+esm works
• https://cdn.jsdelivr.net/npm/plotly.js-dist-min@2.35.3/+esm times out

My guess is that this is an issue with jsdelivr, rather than plotly, but just giving a heads up so you can track it down 🙏

cc: @gvwilson

[archmoj]

Here is the diff between 2.35.3 and 2.35.2:
v2.35.2...v2.35.3

I agree with @duaneatat that this looks like a jsdelivr issue.
plotly.js-dist-min v2.35.3 is published to npm. See https://www.npmjs.com/package/plotly.js-dist-min/v/2.35.3

Also the unminified plotly.js-dist is accessible at: https://cdn.jsdelivr.net/npm/plotly.js-dist@2.35.3/+esm

cc:
@alexcjohnson
@samhinshaw

[gvwilson]

@archmoj will this issue reoccur in the 3.0 release?

[j-dobr]

Still an issue with 3.0.0 and 3.0.1:

• https://cdn.jsdelivr.net/npm/plotly.js-dist@3.0.0/+esm works
• https://cdn.jsdelivr.net/npm/plotly.js-dist-min@3.0.0/+esm 500 Internal Server Error
• https://cdn.jsdelivr.net/npm/plotly.js-dist@3.0.1/+esm works
• https://cdn.jsdelivr.net/npm/plotly.js-dist-min@3.0.1/+esm 500 Internal Server Error

[samhinshaw]

I do agree that is seems this is most likely an issue with the way jsdelivr is repackaging packages published to npm. (Interestingly, 2.53.3 is now available on jsdelivr in the esm format: https://cdn.jsdelivr.net/npm/plotly.js-dist-min@2.35.3/+esm)

In the meantime, a workaround for some may be to use esm.sh. Its CDN may be less robust, but the way it packages seems to be more consistent, producing plotly.js-dist and plotly.js-dist-min bundles of nearly identical size.

• https://esm.sh/plotly.js-dist@3.0.1
• https://esm.sh/plotly.js-dist-min@3.0.1

[gvwilson]

@alexcjohnson what's your preferred solution for this?

[alexcjohnson]

I'm not aware of Plotly ever promoting the use of jsdelivr. I personally have no experience with it or why it would be preferred over cdn.plot.ly, which works with all these versions. (to be clear I'm not saying there's no reason - I just don't know what it is)

So I feel like the most productive path forward here would be for someone who's actually interested in using plotly.js via jsdelivr to contact the jsdelivr team and see if they can track down the issue on their side.

If this effort uncovers something we could do on our side to play nicer with jsdelivr - particularly if it comes with a test so we know we're continuing to abide by whatever constraint this is going forward - then we'd be happy to accept a PR and commit to keeping that test passing going forward. I'll note this does NOT mean we'd be committing to keeping jsdelivr working - we can't do that because we have no control over what they do.