🐞 Patch Changes
- #15004
16f3994Thanks @antonyfaris! - Fixes an issue where Svelte components used in Astro files would incorrectly report type errors when usingclient:*directives.
@astrojs/svelte
🐞 Patch Changes
- #14934
4264a36Thanks @antonyfaris! - Fixes an issue where Svelte 5 components used in Astro files would not have proper type checking and IntelliSense.
- #14934
🐞 Patch Changes
-
#14715
3d55c5dThanks @ascorbic! - Adds support for client hydration ingetContainerRenderer()The
getContainerRenderer()function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually callcontainer.addClientRenderer()with the appropriate client renderer entrypoint.See the
container-with-vitestdemo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.
-
🐞 Patch Changes
- #14621
e3175d9Thanks @GameRoMan! - Updatesviteversion to fix CVE
- #14621
🍿 Minor Changes
-
#14430
78011baThanks @ascorbic! - Adds support for async server renderingSvelte 5.36 added experimental support for async rendering. This allows you to use
awaitin your components in several new places. This worked out of the box with client-rendered components, but server-rendered components needed some extra help. This update adds support for async server rendering in Svelte components used in Astro.To use async rendering, you must enable it in your Svelte config:
svelte.config.js export default {compilerOptions: {experimental: {async: true,},},};Then you can use
awaitin your components:<script>let data = await fetch('/api/data').then(res => res.json());</script><h1>{data.title}</h1>See the Svelte docs for more information on using
awaitin Svelte components, including inside$derivedblocks and directly in markup.
🐞 Patch Changes
-
🐞 Patch Changes
- #14326
c24a8f4Thanks @jsparkdev! - Updatesviteversion to fix CVE
- #14326
🍿 Minor Changes
-
#13809
3c3b492Thanks @ascorbic! - Increases minimum Node.js version to 18.20.8Node.js 18 has now reached end-of-life and should not be used. For now, Astro will continue to support Node.js 18.20.8, which is the final LTS release of Node.js 18, as well as Node.js 20 and Node.js 22 or later. We will drop support for Node.js 18 in a future release, so we recommend upgrading to Node.js 22 as soon as possible. See Astro’s Node.js support policy for more details.
:warning: Important note for users of Cloudflare Pages: The current build image for Cloudflare Pages uses Node.js 18.17.1 by default, which is no longer supported by Astro. If you are using Cloudflare Pages you should override the default Node.js version to Node.js 22. This does not affect users of Cloudflare Workers, which uses Node.js 22 by default.
-
🐞 Patch Changes
- #13731
c3e80c2Thanks @jsparkdev! - update vite to latest version for fixing CVE
- #13731
🐞 Patch Changes
- #13720
e1cd1aeThanks @florian-lefebvre! - Fixes SSR renderer type
- #13720
🐞 Patch Changes
- #13663
a19a185Thanks @florian-lefebvre! - Improves type-safety of renderers
- #13663
🐞 Patch Changes
-
#13596
3752519Thanks @jsparkdev! - update vite to latest version to fix CVE -
#13547
360cb91Thanks @jsparkdev! - Updates vite to the latest version
-
🐞 Patch Changes
- #13526
ff9d69eThanks @jsparkdev! - updateviteto the latest version
- #13526
🐞 Patch Changes
- #13505
a98ae5bThanks @ematipico! - Updates the dependencyviteto the latest.
- #13505
🐞 Patch Changes
- #13323
80926faThanks @ematipico! - Updatesesbuildandviteto the latest to avoid false positives audits warnings caused byesbuild.
- #13323
🐞 Patch Changes
- #12594
4f2fd0aThanks @Princesseuh! - Fixes compatibility with Astro 5
- #12594