Bump the javascript-dependencies group across 1 directory with 3 updates

[dependabot]

Bumps the javascript-dependencies group with 2 updates in the / directory: @astrojs/starlight and sharp.

Updates @astrojs/starlight from 0.21.2 to 0.23.2

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.23.2

Patch Changes

• #1913 7ebe8f75 Thanks @​delucis! - Fixes support for Astro’s build: { format: 'preserve' } configuration option

• #1941 2f3240c9 Thanks @​astrobot-houston! - Adds icon support for .otf files in <FileTree>

@​astrojs/starlight@​0.23.1

Patch Changes

• #1892 01de9be8 Thanks @​delucis! - Internal refactor: simplify some CSS for the <details> element

@​astrojs/starlight@​0.23.0

Minor Changes

• #1846 2de67039 Thanks @​delucis! - Updates @astrojs/mdx to v3 and enables MDX optimization by default

  ⚠️ Potentially breaking change: MDX optimization speeds up builds (Starlight’s docs are building ~40% faster for example), but restricts some advanced MDX features. See full details in the MDX optimization documentation.

  Most Starlight users should be unaffected, but if you are using MDX files outside of Starlight pages with the components prop, you may see issues. You can disable optimization by adding MDX manually to your integrations array in astro.config.mjs:

  import { defineConfig } from 'astro/config';
  + import mdx from '@astrojs/mdx';
  import starlight from '@astrojs/starlight';
  // https://astro.build/config
  export default defineConfig({
  integrations: [
  starlight({
  title: 'My docs',
  // ...
  }),
  
  
    mdx(),
  
  ],
  });

#1735 1a9ab50d Thanks @​HiDeoo! - Adds custom styles for <details> and <summary> elements in Markdown content.

#1846 2de67039 Thanks @​delucis! - ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now 4.8.6

Please update Astro and Starlight together:

npx @astrojs/upgrade

@​astrojs/starlight@​0.22.4

Patch Changes

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.23.2

Patch Changes

• #1913 7ebe8f75 Thanks @​delucis! - Fixes support for Astro’s build: { format: 'preserve' } configuration option

• #1941 2f3240c9 Thanks @​astrobot-houston! - Adds icon support for .otf files in <FileTree>

0.23.1

Patch Changes

• #1892 01de9be8 Thanks @​delucis! - Internal refactor: simplify some CSS for the <details> element

0.23.0

Minor Changes

• #1846 2de67039 Thanks @​delucis! - Updates @astrojs/mdx to v3 and enables MDX optimization by default

  ⚠️ Potentially breaking change: MDX optimization speeds up builds (Starlight’s docs are building ~40% faster for example), but restricts some advanced MDX features. See full details in the MDX optimization documentation.

  Most Starlight users should be unaffected, but if you are using MDX files outside of Starlight pages with the components prop, you may see issues. You can disable optimization by adding MDX manually to your integrations array in astro.config.mjs:

  import { defineConfig } from 'astro/config';
  + import mdx from '@astrojs/mdx';
  import starlight from '@astrojs/starlight';
  // https://astro.build/config
  export default defineConfig({
  integrations: [
  starlight({
  title: 'My docs',
  // ...
  }),
  
  
    mdx(),
  
  ],
  });

#1735 1a9ab50d Thanks @​HiDeoo! - Adds custom styles for <details> and <summary> elements in Markdown content.

#1846 2de67039 Thanks @​delucis! - ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now 4.8.6

Please update Astro and Starlight together:

npx @astrojs/upgrade

... (truncated)

Commits

• aa50ad8 [ci] release (#1929)
• 2f3240c ci: update file icons (#1941)
• 7ebe8f7 Use directory-style path formatting with build.format: 'preserve' (#1913)
• d296855 [ci] format
• 67262f6 [ci] release (#1897)
• 01de9be Micro-optimization: clean up \<details> CSS (#1892)
• 70f12fc [ci] format
• 8f22a97 [ci] release (#1890)
• 1a9ab50 Adds custom styles for \<details> and \<summary> elements in Markdown conte...
• 2de6703 Update @​astrojs/mdx to v3 (#1846)
• Additional commits viewable in compare view

Updates astro from 4.5.12 to 4.9.2

Release notes

Sourced from astro's releases.

[email protected]

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,
  },
  });

[email protected]

Patch Changes

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

[email protected]

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/container';
  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

Updates sharp from 0.33.3 to 0.33.4

Changelog

Sourced from sharp's changelog.

v0.33.4 - 16th May 2024

• Remove experimental status from pipelineColourspace.

• Reduce default concurrency when musl thread over-subscription detected.

• TypeScript: add missing definitions for OverlayOptions. #4048 @​ike-gg

• Install: add advanced option to force use of a globally-installed libvips. #4060

• Expose bilinear resizing kernel (and interpolator). #4061

• Ensure extend operation stays sequential for multi-page TIFF (regression in 0.32.0). #4069

• Tighten validation of constructor text integer properties. #4071

• Simplify internal StaySequential logic. #4074 @​kleisauke

• Ensure negate operation occurs after profile conversion. #4096 @​adriaanmeuris

Commits

• 19d0e27 Release v0.33.4
• 16b764f Prerelease v0.33.4-rc.0
• 1593ee3 Bump devDeps
• 668b5ba Docs: changelog and credit for #4096
• 29336f4 Ensure negate op occurs after profile conversion (#4096)
• b5fddd7 Install: log node-addon-api version if available
• da655a1 Reduce default concurrency for musl thread over-subscription
• 93c615d Bump devDeps
• f325dc3 Refactor to use C++ boolean literals rather than macros
• 0fde71c Ensure all contributor email addresses are valid (#4088)
• 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 <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

[dependabot]

Superseded by #26.