These constants are not used by the library itself internally, but are defined so that the user code can reference them. They are not conventionally exported like they would be from a normal library which can be confusing, but this was a tradeoff we've made to make the user code be as minimal and as quick to script with as possible. See issue #59 as an alternative setup we've considered.

Thanks, I will read it later.

For extra context, the way we run use code is by using eval near the bottom of the file. This allows maybe variables to automatically be in scope without having to import everything, which makes it faster/easier for quickly scripting in the live editor, but more challenging for building standard applications with the library. P5.js also has two different modes that it can operate in for this reason, that linked issue I mentioned is one possible compromise.

eval function here

Hi, PWhiddy

Do you mean P5.js itself also use eval function for live editor and use another method for building the application library? Is there any further information for these two different modes in P5.js codebase (e.g. Github link)? Thank you.

Here is some documentation of p5's "instance mode" vs "global mode"

https://github.com/processing/p5.js/wiki/p5.js-overview#instantiation--namespace