Kenneth Lim

@davepagurek Parallel loading is indeed a potential concern for this. I'm initially thinking just leaning into promises if the syntax don't feel too complicated. ```js let img1, img2, img3; async...

Just in case you haven't catch this, it seems like signing in with username and password is not currently working (server always return 401 incorrect username and password).

For those in contributor docs, we'll fix in the p5.js repo.

@hadenlee node 14 and node 16 are not supported for building node.js anymore (node 14 EOL is only about a month away and default npm version bundled with many versions...

I tried on an M1 machine with macOS 12.5.1 (can't update it to newer versions at the moment) and still cannot replicate, although I doubt the system architecture or OS...

Good news! NPM seems to have finally resolved this bug and I have tested at least npm 8.19.3 which comes with default install of node 18.13.0. I don't know what...

@Bernice55231 For p5.js, it is possible to pass a number string (eg. `"100"`) to functions expecting numbers and it'll work as if the string has been parsed into a string....

Just to note that I find this has been fixed by https://github.com/npm/cli/commit/c7d5a69080b5de6ed0f1cdde77e7d7a3c6b05158 and is available in the latest `npm` release.

@dhowe The idea is to create RFC issues for them as they currently lives in the full RFC document I put together. It is a bit tricky to manage at...

This has been completed