v0.9.20

This fix is a tiny patch added on top of v0.9.19 (which I just released a couple of hours ago). This update prevents JDK24 users from seeing a warning about Kobweb using a restricted method. While I'm not sure exactly how many users would be impacted by it, this would likely happen to new user who installs Kobweb via a package manager who also doesn't explicitly set JAVA_HOME to an older JDK version (probably a bunch of folks).

However, in order for users to see a more useful "What's new" section than just "tiny patch for JDK24 users", we have copied everything from v0.9.19 and put it here as well:

What's New?

• Added ways to help limit live reloading when you don't want it on.

  • kobweb run --once will completely disable the feature for this run.
  • kobweb run and then pressing P will pause / unpause live reloading.
    • Code will still compile continuously! But the server will ignore requests to reload the current page. As a user, you can still reload manually.
    • Requires your project be using Kobweb v0.23.0 or newer, or otherwise this option won't be available.

• The CLI will now offer to restart the server if it detects that conf.yaml has changed.

• If you run kobweb export, it now drops you into an interactive menu to choose the proper export layout instead of defaulting to fullstack.

  • Fullstack vs. static layouts are a feature that bites new users so we hope to make the choice more explicit.
  • See also: https://kobweb.varabyte.com/docs/concepts/foundation/exporting#static-layout-vs-full-stack-sites
  • Specify the layout explicitly to avoid this, i.e. --layout static or --layout fullstack

• After an export, the suggested "kobweb run" message now includes the -p option if relevant

  • For example: Export finished successfully. You can run 'kobweb run -p site --env prod' to preview your site.

• The deprecated kobweb layout value has been removed. (This was renamed to fullstack a while back)

---

Full Changelog (since 0.9.18): v0.9.18...v0.9.20