Streamline JS library bindings #125
Description
This integration is currently enabling well dynamic code execution.
Although it's sub-optimal for exposing directly the functionality of a JS library.
For example: https://github.com/andreaTP/highlightjs4j
Issues:
- first execution still needs a full compilation
- you need to move around the "dist" of an npm build and keep it on the classpath
How things can be better:
- pre-compile at build-time with QuickJs and embed only the result
- disable the caching mechanism and pre-load (even with wizer?) the compiled JS code
Unknowns:
I'm not sure how deep should we go, we should measure pros/cons on specializing this much.
For example: should we embed the compiled JS directly in the wasm payload or there is no benefit?
We need to experiment and come up with a proposal.