You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have recently released p5.js 2.3.0. Before announcing major work on 2.4, we will focus on switching to p5.js 2.0 across the p5.js ecosystem.
This issue is both an update of actions the maintainers plan to take, and an opportunity to flag any concerns or questions. You can comment here, on the issues linked below, or in discord.p5js.org in the #contribute-to-p5 channel.
Timeline
This timeline for p5.js version 2 was first introduced here. We are on track, and in the next 2 months will be implementing the default switch:
Start of April, 2025: release of p5.js v2.0 - available to import, opt-in in the p5.js Editor ✅
End of March, 2026: p5.js v1.x freeze - no further updates ✅ 1.x patches over the past year have been primarily documentation corrections
Now: working on all administrative updates (on the repositories, the website, and the editor) to enable switch to be completed by start of August
Start of August, 2026: p5.js 2.0 is the default version in the p5.js Editor
Note
If this issue is open and pinned, it means it is the most current update of the current milestone, and your input is welcome! Here are the previous milestone updates related to p5.js v2:
Over a year has passed between release of 2.0 and the switch to using it as the default version. This has been intentional, and has given time for the creation of:
More content is being worked on currently, to be released prior to switch. If you notice gaps in content? Proposed content to make the switch smoother is welcome!
What's Next?
You are welcome to monitor 2.4 planning here and get involved in any open discussions! However, review may take a while if there are urgent/emerging topics related to the switch.
We have recently released p5.js 2.3.0. Before announcing major work on 2.4, we will focus on switching to p5.js 2.0 across the p5.js ecosystem.
This issue is both an update of actions the maintainers plan to take, and an opportunity to flag any concerns or questions. You can comment here, on the issues linked below, or in discord.p5js.org in the
#contribute-to-p5channel.Timeline
This timeline for p5.js version 2 was first introduced here. We are on track, and in the next 2 months will be implementing the default switch:
p5.jsso that 2.x is the main branch #8871p5js.org(thebeta.p5js.orglinks continue to work via redirects) p5.js-website#14262.xlatest as the default version p5.js-web-editor#4149Note
If this issue is open and pinned, it means it is the most current update of the current milestone, and your input is welcome! Here are the previous milestone updates related to p5.js v2:
Why?
Over a year has passed between release of 2.0 and the switch to using it as the default version. This has been intentional, and has given time for the creation of:
async/awaitusageMore content is being worked on currently, to be released prior to switch. If you notice gaps in content? Proposed content to make the switch smoother is welcome!
What's Next?
You are welcome to monitor 2.4 planning here and get involved in any open discussions! However, review may take a while if there are urgent/emerging topics related to the switch.