🙈 The PR is closed and the preview is expired.

Can we add a bit more content to the last three sections? At the moment, there are just a list of bullet points.

Also, please update the date of publication.

For my own understanding, are you creating one JS context per call?

What if you want to load JavaScript libraries?

For my own understanding, are you creating one JS context per call?

What if you want to load JavaScript libraries?

Currently yes, there is a single JS context per call. I've added a little bit of information to blog post in the "Future Plans" section about this. There are optimizations that will need to happen. Perhaps a discussion with Quarkus experts will be needed to really nail down the integration. I've focused mostly on the DevEx in this phase. The result is, I think, a really easy way to integrate JS functionality into a Quarkus app. But it's a pretty naive approach, without significant time spent optimizing.

As for javascript libraries, you can use whatever libraries you want (provided they don't use Browser or Node.js APIs that cannot be shimmed). You can even use typescript if you want. The idea is you could have a standard JS build pipeline for your script, with a bundler that produced a final .js file that would get loaded by this feature.

Quickjs4j even outputs a .mjs file for the context functions, so you can have some code completion and proper validation in your IDE.

@cescoffier Updated based on feedback. Thanks for the review.

Merged!