Bump astro from 4.7.1 to 4.8.1

[dependabot]

Bumps astro from 4.7.1 to 4.8.1.

Release notes

Sourced from astro's releases.

astro@4.8.1

Patch Changes

• #10987 05db5f7 Thanks @​ematipico! - Fix a regression where the flag experimental.rewriting was marked mandatory. Is is now optional.

• #10975 6b640b3 Thanks @​bluwy! - Passes the scoped style attribute or class to the <picture> element in the <Picture /> component so scoped styling can be applied to the <picture> element

create-astro@4.8.0

Minor Changes

• #10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @​ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

  This change is in line with Astro's Node.js support policy.

astro@4.8.0

Minor Changes

• #10935 ddd8e49 Thanks @​bluwy! - Exports astro/jsx/rehype.js with utilities to generate an Astro metadata object

• #10625 698c2d9 Thanks @​goulvenclech! - Adds the ability for multiple pages to use the same component as an entrypoint when building an Astro integration. This change is purely internal, and aligns the build process with the behaviour in the development server.

• #10906 7bbd664 Thanks @​Princesseuh! - Adds a new radio checkbox component to the dev toolbar UI library (astro-dev-toolbar-radio-checkbox)

• #10963 61f47a6 Thanks @​delucis! - Adds support for passing an inline Astro configuration object to getViteConfig()

  If you are using getViteConfig() to configure the Vitest test runner, you can now pass a second argument to control how Astro is configured. This makes it possible to configure unit tests with different Astro options when using Vitest’s workspaces feature.

  // vitest.config.ts
  import { getViteConfig } from 'astro/config';
  export default getViteConfig(
  /* Vite configuration /
  { test: {} },
  / Astro configuration */
  {
  site: 'https://example.com',
  trailingSlash: 'never',
  }
  );

• #10867 47877a7 Thanks @​ematipico! - Adds experimental rewriting in Astro with a new rewrite() function and the middleware next() function.

  The feature is available via an experimental flag in astro.config.mjs:

  export default defineConfig({
    experimental: {
      rewriting: true,

... (truncated)

Changelog

Sourced from astro's changelog.

4.8.1

Patch Changes

• #10987 05db5f7 Thanks @​ematipico! - Fix a regression where the flag experimental.rewriting was marked mandatory. Is is now optional.

• #10975 6b640b3 Thanks @​bluwy! - Passes the scoped style attribute or class to the <picture> element in the <Picture /> component so scoped styling can be applied to the <picture> element

4.8.0

Minor Changes

• #10935 ddd8e49 Thanks @​bluwy! - Exports astro/jsx/rehype.js with utilities to generate an Astro metadata object

• #10625 698c2d9 Thanks @​goulvenclech! - Adds the ability for multiple pages to use the same component as an entrypoint when building an Astro integration. This change is purely internal, and aligns the build process with the behaviour in the development server.

• #10906 7bbd664 Thanks @​Princesseuh! - Adds a new radio checkbox component to the dev toolbar UI library (astro-dev-toolbar-radio-checkbox)

• #10963 61f47a6 Thanks @​delucis! - Adds support for passing an inline Astro configuration object to getViteConfig()

  If you are using getViteConfig() to configure the Vitest test runner, you can now pass a second argument to control how Astro is configured. This makes it possible to configure unit tests with different Astro options when using Vitest’s workspaces feature.

  // vitest.config.ts
  import { getViteConfig } from 'astro/config';
  export default getViteConfig(
  /* Vite configuration /
  { test: {} },
  / Astro configuration */
  {
  site: 'https://example.com',
  trailingSlash: 'never',
  }
  );

• #10867 47877a7 Thanks @​ematipico! - Adds experimental rewriting in Astro with a new rewrite() function and the middleware next() function.

  The feature is available via an experimental flag in astro.config.mjs:

  export default defineConfig({
    experimental: {
      rewriting: true,
    },
  });

  When enabled, you can use rewrite() to render another page without changing the URL of the browser in Astro pages and endpoints.

... (truncated)

Commits

• e2cdd3c [ci] release (#10985)
• 05db5f7 fix: incorrect type for experimental option (#10987)
• 3e16858 [ci] format
• 6b640b3 Support scope styles for picture element in Picture component (#10975)
• 25caca0 [ci] format
• f5ff4a5 chore: fix changelog bug caused by changesets bot (#10982)
• 770b9f0 [ci] release (#10944)
• 0ac090d [ci] format
• 814d7c1 chore: move error in the correct section (#10980)
• 3545360 [ci] format
• 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)