🐞 Patch Changes
- #13591
5dd2d3fThanks @florian-lefebvre! - Removes unused code
@astrojs/node
🍿 Minor Changes
-
#13527
2fd6a6bThanks @ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:
---export const prerender = false; // Not needed with 'server' outputconst cart = await Astro.session.get('cart');---<a href="/checkout">🛒 {cart?.length ?? 0} items</a>Configuring session storage
Sessions require a storage driver to store the data. The Node, Cloudflare and Netlify adapters automatically configure a default driver for you, but other adapters currently require you to specify a custom storage driver in your configuration.
If you are using an adapter that doesn’t have a default driver, or if you want to choose a different driver, you can configure it using the
sessionconfiguration option:import { defineConfig } from 'astro/config';import vercel from '@astrojs/vercel';export default defineConfig({adapter: vercel(),session: {driver: 'upstash',},});Using sessions
Sessions are available in on-demand rendered pages, API endpoints, actions and middleware.
In pages and components, you can access the session using
Astro.session:---const cart = await Astro.session.get('cart');---<a href="/checkout">🛒 {cart?.length ?? 0} items</a>In endpoints, actions, and middleware, you can access the session using
context.session:export async function GET(context) {const cart = await context.session.get('cart');return Response.json({ cart });}If you attempt to access the session when there is no storage driver configured, or in a prerendered page, the session object will be
undefinedand an error will be logged in the console:---export const prerender = true;const cart = await Astro.session?.get('cart'); // Logs an error. Astro.session is undefined---Upgrading from Experimental to Stable
If you were previously using the experimental API, please remove the
experimental.sessionflag from your configuration:import { defineConfig } from 'astro/config';import node from '@astrojs/node';export default defineConfig({adapter: node({mode: "standalone",}),experimental: {session: true,},});See the sessions guide for more information.
-
🐞 Patch Changes
- Updated dependencies [
042d1de]:- @astrojs/internal-helpers@0.6.1
- Updated dependencies [
🐞 Patch Changes
- Updated dependencies [
1e11f5e]:- @astrojs/internal-helpers@0.6.0
- Updated dependencies [
🐞 Patch Changes
- #13190
c6bf6b3Thanks @lee-arnold! - Fixes the image endpoint entrypoint
- #13190
🍿 Minor Changes
-
#13145
8d4e566Thanks @ascorbic! - Automatically configures filesystem storage when experimental session enabledIf the
experimental.sessionflag is enabled when using the Node adapter, Astro will automatically configure session storage using the filesystem driver. You can still manually configure session storage if you need to use a different driver or want to customize the session storage configuration.See the experimental session docs for more information on configuring session storage.
-
✨ Major Changes
-
#11679
ea71b90Thanks @florian-lefebvre! - Adds stable support forastro:env -
#11770
cfa6a47Thanks @Princesseuh! - Removed support for the Squoosh image service. As the underlying librarylibsquooshis no longer maintained, and the image service sees very little usage we have decided to remove it from Astro.Our recommendation is to use the base Sharp image service, which is more powerful, faster, and more actively maintained.
import { squooshImageService } from "astro/config";import { defineConfig } from "astro/config";export default defineConfig({image: {service: squooshImageService()}});If you are using this service, and cannot migrate to the base Sharp image service, a third-party extraction of the previous service is available here: https://github.com/Princesseuh/astro-image-service-squoosh
-
🐞 Patch Changes
-
#11535
932bd2eThanks @matthewp! - Move polyfills up before awaiting the env module in the Node.js adapter.Previously the env setting was happening before the polyfills were applied. This means that if the Astro env code (or any dependencies) depended on
crypto, it would not be polyfilled in time.Polyfills should be applied ASAP to prevent races. This moves it to the top of the Node adapter.
-
🐞 Patch Changes
- #11296
5848d97Thanks @florian-lefebvre! - Fixesastro:envgetSecret compatibility
- #11296
🍿 Minor Changes
- #11199
2bdca27Thanks @florian-lefebvre! - Adds support for experimentalastro:envreleased in Astro 4.10
- #11199
🐞 Patch Changes
- #11202
d0248bcThanks @dkobierski! - Fixes suppressed logs when error occurs
- #11202
🐞 Patch Changes
- #10491
28e33a2f9c04373eae5da2e6edb0dc2981bce790Thanks @castarco! - Fixes a bug where the preview server wrongly appends trailing slashes to subresource URLs.
- #10491
🐞 Patch Changes
- #10454
83f9105cd50e2756d02ca2be73ab84f9d582d3f8Thanks @lilnasy! - Prevents crashes caused by rejections of offshoot promises.
- #10454
🐞 Patch Changes
- #10285
d5277df5a4d1e9a8a7b6c8d7b87912e13a163f7fThanks @Princesseuh! - Fixes an issue where malformed requests could cause the server to error in certain cases.
- #10285
🐞 Patch Changes
- #10282
b47dcaa25968ec85ba96fce23381c94a94e389f6Thanks @SatanshuMishra! - Fixes theserver.hostoption to properly listen on all network interfaces when set totrue
- #10282
🐞 Patch Changes
- #10208
8cd38f02456640c063552aef00b2b8a216b3935dThanks @log101! - Fixes custom headers are not added to the Node standalone server responses in preview mode
- #10208
🍿 Minor Changes
- #9143
041fdd5c89920f7ccf944b095f29e451f78b0e28Thanks @ematipico! - Adds experimental support for internationalization domains
- #9143