plotly / plotly/react-plotly.js

How to use plotly.js-dist with react-plotly.js?

Open
#258 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.1k
Forks
138
Avg merge
3d 2h
Merged PRs (30d)
4

Description

As per below issue, we were instructed to switch from plotly.js to plotly.js-dist to work around an error with plotly.js version 2.5.0. However, in doing this we then get errors when trying to import from react-plotly.js. Is there a way to use react-plotly.js with plotly.js-dist?

What's the reasoning behind not using ploly.js-dist then?

We're actually using react-plotly in our React project. Switching from plotly.js to plotly.js-dist resolves the npm ci issue but we then get errors when importing from react-plotly.js. Is there a way to use react-plotly with plotly.js-dist?

image

I see. Please open an issue or pull request on react-plotly.js and paste the link here.

Originally posted by @archmoj in https://github.com/plotly/plotly.js/issues/5925#issuecomment-913690061

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported npm ci and import errors with react-plotly.js and plotly.js-dist in a minimal React project. Review the linked plotly.js discussion for context, then verify whether the two packages can be used together and document the supported setup or remaining incompatibility.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
data-visualization, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.