processing / processing/p5.js-web-editor
Library Management
Open
Nobody has claimed this yet.
Area: Design
Feature Request
Priority:Medium
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 1.7k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 8
Description
While we ultimately will likely want "library manager" like features we should probably start with p5.dom and p5.sound included by default.
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
The issue proposes including p5.dom and p5.sound by default, while leaving a broader library manager for later. Start by locating the editor's current dependency or library-loading entry point, then confirm the expected default behavior and how it can be tested. Done means both libraries are available by default without requiring user configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100