Closed zachsa closed 1 year ago
This is correct - if you look at the package on npm you will see that it is a malicious package that is made to confuse users of the real d3
- https://www.npmjs.com/package/d3.js.
We should have better exception handling around cases like this to report what is going on.
Ah sorry. Here is the link https://www.npmjs.com/package/d3?activeTab=versions.
I didn't realize d3.js isn't the correct name. However it's the real package that is broken
I see. That wasn't working this morning when I tested that.
Hi,
d3.js@7.7.0
does not seem to be available yet, although I did request a build via the build API yesterday. Usually this is quite quick, so I suspect there may be a problem with this particular package