Performance improvement: Puppeteer for fabric.js
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 374
- PR merge metrics
- No merged PRs in 30d
Description
Could potentially increase performance, because I believe chromium's canvas is faster that node-canvas
But we need to bridge between node.js and chromium and send big frames of raw data (~100MB) back and forth.
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
No files, tests, or entry points are named. Start by locating the fabric.js rendering path and assessing the proposed Puppeteer/Chromium bridge against node-canvas, including transfers of roughly 100MB of raw data. Done would require an agreed design and measured performance evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100