[p5.js 2.0 RFC Proposal]: use lighter dependency

[asukaminato0721]

Increasing access

p5.js use some sub-dependency which use unnecessary spaces. So use lighter dependencies.

Which types of changes would be made?

• Breaking change (Add-on libraries or sketches will work differently even if their code stays the same.)
• Systemic change (Many features or contributor workflows will be affected.)
• Overdue change (Modifications will be made that have been desirable for a long time.)
• Unsure (The community can help to determine the type of change.)

Most appropriate sub-area of p5.js?

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

What's the problem?

try to reduce a bit of build size/npm install size.

What's the solution?

use https://github.com/SukkaW/nolyfill

Pros (updated based on community comments)

Example list:

• Consistency: This proposal will not affect current behavior...
• Size: This proposal will reduce the build/download size.

Cons (updated based on community comments)

• require node >= 12 but currently it's already node >= 20

Proposal status

Under review

[limzykenneth]

I think this is no longer necessary as we are only using eslint itself and not the referenced eslint plugins dependencies.