Missing ndarray dependencies using plotly.js v2.5.0, npm v6 and react-plotly.js v1
See original GitHub issueWhen reviewing our weekly Dependabot updates I came across an issue with our migration from Plotly 2.4.1 to 2.5.0. We now get the error shown below when trying to install dependencies. The issue was shown in our CI pipeline which runs npm ci
.
I’ve attached our package files from 2.4.1 which work fine and the updated ones from 2.5.0 which break. You can run npm ci
with the 2.5.0 files to reproduce.
Issue Analytics
- State:
- Created 2 years ago
- Comments:40 (20 by maintainers)
Top Results From Across the Web
v2.6.0 Milestone · GitHub
Open-source JavaScript charting library behind Plotly and Dash - v2.6.0 Milestone ... Missing ndarray dependencies using plotly.js v2.5.0, npm v6 and ...
Read more >plotly.js - npm
The open source javascript graphing library that powers plotly. Latest version: 2.16.3, last published: 12 days ago. Start using plotly.js ...
Read more >React plotly.js in JavaScript
This React component takes the chart type, data, and styling as Plotly JSON in its data and layout props, then draws the chart...
Read more >How to import plotly.js into TypeScript? - Stack Overflow
This allows you to use the plain Javascript version inside Typescript. ... It was because react-plotly.js was being bundled in the 'dependencies`.
Read more >plotly.js-basic-dist | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@archmoj I’ve forked my own version of your branch and removed src from npmignore. I can now confirm that your PR is working as expected with npm version 6.
Unfortunately this week we may not be able to allocate more time investigating this problem. But please let us know if you found a solution for this namely at the
react-plotly.js
level.