PolicyEngine / PolicyEngine/policyengine-app-v2
Remove react-plotly.js once all migratable charts are done
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 3
- Avg merge
- 1d 50m
- Merged PRs (30d)
- 39
Description
Summary
Once all feasible chart components are migrated away from Plotly (see #609, #663), remove react-plotly.js and plotly.js from the dependency tree to reduce bundle size significantly.
Prerequisites
- #663 merged (16 charts migrated to Recharts)
- Remaining Plotly-only charts either migrated to alternatives or confirmed as permanently needing Plotly
- Blog/notebook Plotly JSON rendering evaluated for alternatives
Current Plotly footprint
plotly.js adds ~3MB to the bundle (minified). Even with code splitting, it's a significant chunk. If we can eliminate all Plotly usage, the savings are substantial.
What needs to happen
- Migrate or confirm each remaining Plotly chart (tracked separately)
- If blog/notebook Plotly JSON must stay, consider lazy-loading Plotly only for those routes
- Remove
react-plotly.jsandplotly.jsfrompackage.json - Remove Plotly mock from test setup (
vitest.setup.mjs) - Update
.claude/skills/chart-standards.mdto remove Plotly references
Context
Related: #609, #663
Contributor guide
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 by checking prerequisites #663 and #609, then audit the remaining Plotly-only charts and the blog/notebook Plotly JSON rendering. Review package.json, vitest.setup.mjs, and .claude/skills/chart-standards.md. Done means remaining charts are migrated or confirmed, Plotly dependencies and mocks are removed, and Plotly references in the chart standards are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- documentation, frontend, performance, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100