Sourced from @​astrojs/node's releases.

@​astrojs/node@​9.3.0

Minor Changes

• #14012 a125a14 Thanks @​florian-lefebvre! - Adds a new experimental configuration option experimentalDisableStreaming to allow you to opt out of Astro's default HTML streaming for pages rendered on demand.

  HTML streaming helps with performance and generally provides a better visitor experience. In most cases, disabling streaming is not recommended.

  However, when you need to disable HTML streaming (e.g. your host only supports non-streamed HTML caching at the CDN level), you can now opt out of the default behavior:

  import { defineConfig } from 'astro/config';
  import node from '@astrojs/node';
  export default defineConfig({
  adapter: node({
  mode: 'standalone',
  
  experimentalDisableStreaming: true,
  }),
  });
  

#13972 db8f8be Thanks @​ematipico! - Adds support for the experimental static headers Astro feature.

When the feature is enabled via the option experimentalStaticHeaders, and experimental Content Security Policy is enabled, the adapter will generate Response headers for static pages, which allows support for CSP directives that are not supported inside a <meta> tag (e.g. frame-ancestors).

import { defineConfig } from 'astro/config';
import node from '@astrojs/node';
export default defineConfig({
adapter: node({
mode: 'standalone',
experimentalStaticHeaders: true,
}),
experimental: {
cps: true,
},
});

Sourced from @​astrojs/node's changelog.

9.3.0

Minor Changes

• #14012 a125a14 Thanks @​florian-lefebvre! - Adds a new experimental configuration option experimentalDisableStreaming to allow you to opt out of Astro's default HTML streaming for pages rendered on demand.

  HTML streaming helps with performance and generally provides a better visitor experience. In most cases, disabling streaming is not recommended.

  However, when you need to disable HTML streaming (e.g. your host only supports non-streamed HTML caching at the CDN level), you can now opt out of the default behavior:

  import { defineConfig } from 'astro/config';
  import node from '@astrojs/node';
  export default defineConfig({
  adapter: node({
  mode: 'standalone',
  
  experimentalDisableStreaming: true,
  }),
  });
  

#13972 db8f8be Thanks @​ematipico! - Adds support for the experimental static headers Astro feature.

When the feature is enabled via the option experimentalStaticHeaders, and experimental Content Security Policy is enabled, the adapter will generate Response headers for static pages, which allows support for CSP directives that are not supported inside a <meta> tag (e.g. frame-ancestors).

import { defineConfig } from 'astro/config';
import node from '@astrojs/node';
export default defineConfig({
adapter: node({
mode: 'standalone',
experimentalStaticHeaders: true,
}),
experimental: {
cps: true,
},
});

• 88b54d3 [ci] release (#14033)
• a125a14 feat(node): experimentalDisableStreaming (#14012)
• 98853ce [ci] format
• db8f8be feat(node): experimental static headers (#13972)
• 33f2d15 chore: upgrade to Biome v2 (#13984)
• See full diff in compare view

Sourced from astro's releases.

astro@5.11.0

Minor Changes

• #13972 db8f8be Thanks @​ematipico! - Updates the NodeApp.match() function in the Adapter API to accept a second, optional parameter to allow adapter authors to add headers to static, prerendered pages.

  NodeApp.match(request) currently checks whether there is a route that matches the given Request. If there is a prerendered route, the function returns undefined, because static routes are already rendered and their headers cannot be updated.

  When the new, optional boolean parameter is passed (e.g. NodeApp.match(request, true)), Astro will return the first matched route, even when it's a prerendered route. This allows your adapter to now access static routes and provides the opportunity to set headers for these pages, for example, to implement a Content Security Policy (CSP).

Patch Changes

• #14029 42562f9 Thanks @​ematipico! - Fixes a bug where server islands wouldn't be correctly rendered when they are rendered inside fragments.

  Now the following examples work as expected:

  ---
  import { Cart } from '../components/Cart.astro';
  ---
  <>
  <Cart server:defer />
  </>
  <Fragment slot="rest">
  <Cart server:defer>
  <div slot="fallback">Not working</div>
  </Cart>
  </Fragment>
  

• #14017 8d238bc Thanks @​dmgawel! - Fixes a bug where i18n fallback rewrites didn't work in dynamic pages.

astro@5.10.2

Patch Changes

• #14000 3cbedae Thanks @​feelixe! - Fix routePattern JSDoc examples to show correct return values

• #13990 de6cfd6 Thanks @​isVivek99! - Fixes a case where astro:config/client and astro:config/server virtual modules would not contain config passed to integrations updateConfig() during the build

• #14019 a160d1e Thanks @​ascorbic! - Removes the requirement to set type: 'live' when defining experimental live content collections

  Previously, live collections required a type and loader configured. Now, Astro can determine that your collection is a live collection without defining it explicitly.

  This means it is now safe to remove type: 'live' from your collections defined in src/live.config.ts:

  import { defineLiveCollection } from 'astro:content';
  import { storeLoader } from '@mystore/astro-loader';
  

... (truncated)

Sourced from astro's changelog.

5.11.0

Minor Changes

• #13972 db8f8be Thanks @​ematipico! - Updates the NodeApp.match() function in the Adapter API to accept a second, optional parameter to allow adapter authors to add headers to static, prerendered pages.

  NodeApp.match(request) currently checks whether there is a route that matches the given Request. If there is a prerendered route, the function returns undefined, because static routes are already rendered and their headers cannot be updated.

  When the new, optional boolean parameter is passed (e.g. NodeApp.match(request, true)), Astro will return the first matched route, even when it's a prerendered route. This allows your adapter to now access static routes and provides the opportunity to set headers for these pages, for example, to implement a Content Security Policy (CSP).

Patch Changes

• #14029 42562f9 Thanks @​ematipico! - Fixes a bug where server islands wouldn't be correctly rendered when they are rendered inside fragments.

  Now the following examples work as expected:

  ---
  import { Cart } from '../components/Cart.astro';
  ---
  <>
  <Cart server:defer />
  </>
  <Fragment slot="rest">
  <Cart server:defer>
  <div slot="fallback">Not working</div>
  </Cart>
  </Fragment>
  

• #14017 8d238bc Thanks @​dmgawel! - Fixes a bug where i18n fallback rewrites didn't work in dynamic pages.

5.10.2

Patch Changes

• #14000 3cbedae Thanks @​feelixe! - Fix routePattern JSDoc examples to show correct return values

• #13990 de6cfd6 Thanks @​isVivek99! - Fixes a case where astro:config/client and astro:config/server virtual modules would not contain config passed to integrations updateConfig() during the build

• #14019 a160d1e Thanks @​ascorbic! - Removes the requirement to set type: 'live' when defining experimental live content collections

  Previously, live collections required a type and loader configured. Now, Astro can determine that your collection is a live collection without defining it explicitly.

  This means it is now safe to remove type: 'live' from your collections defined in src/live.config.ts:

  import { defineLiveCollection } from 'astro:content';
  

... (truncated)

• 88b54d3 [ci] release (#14033)
• 42562f9 fix(render): server islands in fragments (#14029)
• db8f8be feat(node): experimental static headers (#13972)
• eb39f8e [ci] format
• 8d238bc fix i18n fallback rewrites failing in server mode (#14017)
• 5891056 [ci] release (#14007)
• 508e6bf [ci] format
• a160d1e Make "type" optional when defining live collections (#14019)
• 041a37d [ci] format
• 33f2d15 chore: upgrade to Biome v2 (#13984)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions