Added a way to register JS modules directly #69
Merged
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.
This MR provides the ability parse the
[js_modules.main]
and[js_modules.worker]
config entries in a source -> target manner so that it's possible to declare any JS module (as standard ECMAScript Module, aka: ESM) that would be automatically available viapolyscript.js_modules
reference.Modules that are on main only and don't have any worker counterpart are fetched on the fly in workers.
Modules that require also companion CSS styles can be defined by providing a
.css
href and still pointing at the same module name, as that gets resolved lazily as opposite of landing out of the box any CSS that's present in the config.Example
The wonderful leaflet has been used to demo both main and worker case.
TODOs