Info about the Svelte version used

[aburaihan66]

These types of layouts have nothing to do with Inertia per se, but simply use the Svelte component model (box: "Info on the Svelte version used"). This also results in the crucial disadvantage that both the specific components of the page and all shared components in the layout are re-rendered every time the page is changed.

The current state of the components in the myanmar gambling data layout is lost and the browser has more work to do to completely recreate the DOM. To counteract this, Inertia provides a functionality for persistent layouts.

The declaration of the layout is not made in the page component, but delegated to Inertia. In this way, Inertia can ensure that only the specific content of the page is re-rendered. Shared components are retained along with their state. User management should also make use of this mechanism in the form of a layout for all public pages.

Between the creation of the first and second parts of this series, new major versions of both Svelte and Inertia were released. Svelte 5 in particular brings a number of changes to the syntax of the component code, but is still fully backwards compatible so that existing code does not need to be changed. This article therefore continues to use the Svelte 4 syntax so that the code examples are consistent across both parts.