processing
Node.js Upgrade Version 16 -> 22
Currently in progress of updating our Node.js version (which is deprecated) to v22.
@katara-Jayprakash, yes, upgrading directly from Node 16 to 22 would introduce some breaking changes, so we're handling the upgrade incrementally. This allows us to ensure the site remains stable as we address any compatibility issues.
ok sound cool , can i also work on this issue too lets refactor this whole web editor website to node 22 with some sort of additional things . is there any specific mailing app that p5.js uses for the communication ?
Hi @raclim,
I wanted to ask if there are any updates on upgrading the p5.js Web Editor to the latest versions of Node.js or MongoDB. Are you currently working on this, or is there any help needed from the community? Also, would it be helpful to schedule a quick community meeting to discuss these upgrades?
Thanks!
Hii @raclim @katara-Jayprakash
Just curious why not just upgrade it to v23 or v24 since they are now stable and also if this upgrade gonna take time then lets just upgrade it to v23 or v24 lets break once and make it more future proof.
let me know your thoughts on this!!
i am thinking of making it, whats your thoughts should we go for it? or wait or maintainers replay
Thanks again for your interest in this issue @katara-Jayprakash and @yesahem!
I've currently assigned this issue to myself, as we generally prefer project maintainers to handle larger refactoring or upgrades that touch deeper parts of the codebase. I'm working on this in tandem with the MongoDB upgrade, which has a deadline at the end of the month, so both are on track to be wrapped up within the next week or so.
While upgrading directly to the latest Node.js version could be possible, I'm opting for a more incremental approach to reduce the risk of breaking changes and ensuring that new changes are easier to track and test, especially since we currently have a few ongoing projects at the moment and want to avoid introducing any disruptions.
Since this issue is currently already in progress, I'd recommend picking up a different issue for now. Please be sure to review the contributor documentation and pinned issue before getting started to make sure everything goes smoothly!