Bump astro from 4.5.12 to 4.9.2 in /astro-site

[dependabot]

Bumps astro from 4.5.12 to 4.9.2.

Release notes

Sourced from astro's releases.

astro@4.9.2

Patch Changes

• #11138 98e0372 Thanks @​ematipico! - You can now pass props when rendering a component using the Container APIs:

  import { experimental_AstroContainer as AstroContainer } from 'astro/contaienr';
  import Card from '../src/components/Card.astro';
  const container = await AstroContainer.create();
  const result = await container.renderToString(Card, {
  props: {
  someState: true,
  },
  });

astro@4.9.1

Patch Changes

• #11129 4bb9269 Thanks @​matthewp! - Prevent errors from adapters when i18n domains is not used

astro@4.9.0

Minor Changes

• #11051 12a1bcc Thanks @​ematipico! - Introduces an experimental Container API to render .astro components in isolation.

  This API introduces three new functions to allow you to create a new container and render an Astro component returning either a string or a Response:

  • create(): creates a new instance of the container.
  • renderToString(): renders a component and return a string.
  • renderToResponse(): renders a component and returns the Response emitted by the rendering phase.

  The first supported use of this new API is to enable unit testing. For example, with vitest, you can create a container to render your component with test data and check the result:

  import { experimental_AstroContainer as AstroContainer } from 'astro/container';
  import { expect, test } from 'vitest';
  import Card from '../src/components/Card.astro';
  test('Card with slots', async () => {
  const container = await AstroContainer.create();
  const result = await container.renderToString(Card, {
  slots: {
  default: 'Card content',
  },
  });
  expect(result).toContain('This is a card');
  expect(result).toContain('Card content');

... (truncated)

Changelog

Sourced from astro's changelog.

4.9.2

Patch Changes

• #11138 98e0372 Thanks @​ematipico! - You can now pass props when rendering a component using the Container APIs:

  import { experimental_AstroContainer as AstroContainer } from 'astro/contaienr';
  import Card from '../src/components/Card.astro';
  const container = await AstroContainer.create();
  const result = await container.renderToString(Card, {
  props: {
  someState: true,
  },
  });

4.9.1

Patch Changes

• #11129 4bb9269 Thanks @​matthewp! - Prevent errors from adapters when i18n domains is not used

4.9.0

Minor Changes

• #11051 12a1bcc Thanks @​ematipico! - Introduces an experimental Container API to render .astro components in isolation.

  This API introduces three new functions to allow you to create a new container and render an Astro component returning either a string or a Response:

  • create(): creates a new instance of the container.
  • renderToString(): renders a component and return a string.
  • renderToResponse(): renders a component and returns the Response emitted by the rendering phase.

  The first supported use of this new API is to enable unit testing. For example, with vitest, you can create a container to render your component with test data and check the result:

  import { experimental_AstroContainer as AstroContainer } from 'astro/container';
  import { expect, test } from 'vitest';
  import Card from '../src/components/Card.astro';
  test('Card with slots', async () => {
  const container = await AstroContainer.create();
  const result = await container.renderToString(Card, {
  slots: {
  default: 'Card content',
  },
  });

... (truncated)

Commits

• cdf89a1 [ci] release (#11140)
• 5af99dc [ci] format
• 98e0372 feat: pass props to container (#11138)
• 4c7949d [ci] release (#11132)
• 4bb9269 Prevent errors from adapters when i18n domains is not used (#11129)
• 5077592 [ci] release (#11116)
• 9566fa0 Actions: Allow actions to be called on the server (#11088)
• e71348e [docs] fix config reference code formatting (#11119)
• 7bfe8aa [ci] format
• c7386ef [docs] update heading level in config reference (#11118)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #209.