search

hendriknielaender / double-trouble

Dev Blog
https://double-trouble.dev
MIT License
11 stars 2 forks source link

chore(deps-dev): bump astro from 4.2.6 to 4.3.2 #401

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 7 months ago

Bumps astro from 4.2.6 to 4.3.2.

Release notes

Sourced from astro's releases.

astro@4.3.2

Patch Changes

astro@4.3.1

Patch Changes

astro@4.3.0

Minor Changes

  • #9839 58f9e393a188702eef5329e41deff3dcb65a3230 Thanks @​Princesseuh! - Adds a new ComponentProps type export from astro/types to get the props type of an Astro component.

    ---
import type { ComponentProps } from 'astro/types';
import { Button } from './Button.astro';

    type myButtonProps = ComponentProps<typeof Button>;

  • #9159 7d937c158959e76443a02f740b10e251d14dbd8c Thanks @​bluwy! - Adds CLI shortcuts as an easter egg for the dev server:

    • o + enter: opens the site in your browser
    • q + enter: quits the dev server
    • h + enter: prints all available shortcuts

  • #9764 fad4f64aa149086feda2d1f3a0b655767034f1a8 Thanks @​matthewp! - Adds a new build.format configuration option: 'preserve'. This option will preserve your source structure in the final build.

    The existing configuration options, file and directory, either build all of your HTML pages as files matching the route name (e.g. /about.html) or build all your files as index.html within a nested directory structure (e.g. /about/index.html), respectively. It was not previously possible to control the HTML file built on a per-file basis.

    One limitation of build.format: 'file' is that it cannot create index.html files for any individual routes (other than the base path of /) while otherwise building named files. Creating explicit index pages within your file structure still generates a file named for the page route (e.g. src/pages/about/index.astro builds /about.html) when using the file configuration option.

    Rather than make a breaking change to allow build.format: 'file' to be more flexible, we decided to create a new build.format: 'preserve'.

    The new format will preserve how the filesystem is structured and make sure that is mirrored over to production. Using this option:

... (truncated)

Changelog

Sourced from astro's changelog.

4.3.2

Patch Changes

4.3.1

Patch Changes

4.3.0

Minor Changes

  • #9839 58f9e393a188702eef5329e41deff3dcb65a3230 Thanks @​Princesseuh! - Adds a new ComponentProps type export from astro/types to get the props type of an Astro component.

    ---
import type { ComponentProps } from 'astro/types';
import Button from './Button.astro';

    type myButtonProps = ComponentProps<typeof Button>;

  • #9159 7d937c158959e76443a02f740b10e251d14dbd8c Thanks @​bluwy! - Adds CLI shortcuts as an easter egg for the dev server:

    • o + enter: opens the site in your browser
    • q + enter: quits the dev server
    • h + enter: prints all available shortcuts

  • #9764 fad4f64aa149086feda2d1f3a0b655767034f1a8 Thanks @​matthewp! - Adds a new build.format configuration option: 'preserve'. This option will preserve your source structure in the final build.

    The existing configuration options, file and directory, either build all of your HTML pages as files matching the route name (e.g. /about.html) or build all your files as index.html within a nested directory structure (e.g. /about/index.html), respectively. It was not previously possible to control the HTML file built on a per-file basis.

    One limitation of build.format: 'file' is that it cannot create index.html files for any individual routes (other than the base path of /) while otherwise building named files. Creating explicit index pages within your file structure still generates a file named for the page route (e.g. src/pages/about/index.astro builds /about.html) when using the file configuration option.

    Rather than make a breaking change to allow build.format: 'file' to be more flexible, we decided to create a new build.format: 'preserve'.

... (truncated)

Commits


Dependabot compatibility score

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 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)