ES6 Conversion Continued and Modularization
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24k
- Forks
- 3.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 25
Description
Increasing Access
This is a pre-existing request whose discussion thread was closed and the conversation has fragmented.
Reopening to consolidate work and discussion here.
Most appropriate sub-area of p5.js?
- Accessibility
- Color
- Core/Environment/Rendering
- Data
- DOM
- Events
- Image
- IO
- Math
- Typography
- Utilities
- WebGL
- Build Process
- Unit Testing
- Internalization
- Friendly Errors
- Other (specify if possible)
Feature enhancement details
AIM: To enable tree-shaking of necessary code, organization, idiomatic style, and to lay a foundation for other future enhancements like WebGPU.
The latest conversation this is being continued from is here https://github.com/processing/p5.js/pull/6173.
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 reviewing the prior discussion in pull request #6173 and the goals stated here: tree-shaking, modularization, and idiomatic organization. The work is done when a concrete modularization plan and implementation are established that enable tree-shaking and support future enhancements such as WebGPU.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100