plotly / plotly/react-plotly.js
Bail out to client-side rendering: next/dynamic
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 138
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 4
Description
i created a next js app and i imported plotly dynamically and set ssr = false as it's nor ssr compatible i tried several other thing to get the result that i want but still get the same bad performance (it takes about 12 secs to load the page) and 22mb of resources (i just use 6 sqlite3 databases that the summation of all of them would not be over 50kb)
i used two line charts in my code
if any further information needs please ask me to provide you
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Next.js app's use of next/dynamic and its two line charts, then reproduce the reported 12-second load and 22 MB of resources. Check whether the six SQLite databases or chart loading accounts for the cost. Done means a reproducible case and a documented performance cause or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, next.js, react, sqlite
- Domain
- data-visualization, frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100