Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm currently in the process of converting all modules that are not worked on by someone immediately into using the new module syntax, ie. not Typography, FES, or WebGL, these can be converted at the implementers' own discretion.
Do have a look at the already converted ones for guidance on how to convert or let me know if further clarifications are needed. I'll outline below.
Each folder inside
src/
is considered a module (ie. if we were to distribute the library in modular form, these are not likely to be further split up). Each file inside of each module is considered a submodule/library file and uses the new library syntax as described in #7015. In addition, each module folder will have a new fileindex.js
which comes in the form:The bundler entry point
app.js
will then import these index file and passp5
to the exported default function, kick starting the module linking process. To put it shortly, the convention/syntax described above plus some minor details I omitted here is to enable the different use cases needed. In addition to global mode and instance mode, the following:ES6 modular import
Script tag modular library import