[p5.js 2.0+ Bug Report]: Reference docs for RC include 2 private methods

[ksen0]

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• WebGPU
• p5.strands
• Build process
• Unit testing
• Internationalization
• Friendly errors
• Other (specify if possible)

p5.js version

2.3.1-rc.2

Web browser and version

No response

Operating system

No response

Steps to reproduce this

Steps:

In p5.js-website:

1. npm run build:reference whih clones p5.js
2. npm run dev
3. Observe, some internal methods are visible, which should not be. Both are marked @private and @internal but this is apparently ignored? It does work for many other methods. Possibly build reference script should be updated?

[ksen0]

@perminder-17 @limzykenneth FYI, I will work on this in the next couple of days unless one of you wants to / already knows what the problem is. My current intent is to see if I can find/add a check for private tag filter in he build script...