This fix is a tiny patch. It fixes a broken message that provides the wrong instructions after a user finishes an export that was introduced as part of a new feature (it would include the -p arg even when it shouldn't have).
However, in order for users to see a more useful "What's new" section when they visit here, we have copied everything from our earlier release 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 --oncewill completely disable the feature for this run.kobweb runand then pressingPwill 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.yamlhas 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 staticor--layout fullstack
-
After an export, the suggested "kobweb run" message now includes the
-poption if relevant- For example:
Export finished successfully. You can run 'kobweb run -p site --env prod' to preview your site.
- For example:
-
The deprecated
kobweblayout value has been removed. (This was renamed tofullstacka while back)
Full Changelog (since 0.9.18): v0.9.18...v0.9.21