Bump the npm group across 1 directory with 4 updates

[dependabot]

Bumps the npm group with 4 updates in the / directory: @astrojs/tailwind, astro, sharp and daisyui.

Updates @astrojs/tailwind from 6.0.0 to 6.0.2

Release notes

Sourced from @​astrojs/tailwind's releases.

@​astrojs/tailwind@​6.0.2

Patch Changes

• #13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

@​astrojs/tailwind@​6.0.1

Patch Changes

• #13471 020c542 Thanks @​delucis! - Updates the README to indicate that the Tailwind integration is deprecated

Changelog

Sourced from @​astrojs/tailwind's changelog.

6.0.2

Patch Changes

• #13505 a98ae5b Thanks @​ematipico! - Updates the dependency vite to the latest.

6.0.1

Patch Changes

• #13471 020c542 Thanks @​delucis! - Updates the README to indicate that the Tailwind integration is deprecated

Commits

• b33cc17 [ci] release (#13504)
• a98ae5b fix: update vite (#13505)
• 6b90200 [ci] release (#13460)
• 9a0808c fix(deps): update all non-major dependencies (#13440)
• f49155f Small change to linking style (#13472)
• 020c542 Add deprecation notice to Tailwind integration README (#13471)
• 2f039b9 Revert "Replace internal cssScopeTo implementation to vite.cssScopeTo" (#13420)
• 725bc0d fix(deps): update all non-major dependencies (#13387)
• d83f92a Replace internal cssScopeTo implementation to vite.cssScopeTo (#13347)
• 16d6d41 fix(deps): update all non-major dependencies (#13346)
• Additional commits viewable in compare view

Updates astro from 5.2.3 to 5.6.1

Release notes

Sourced from astro's releases.

astro@5.6.1

Patch Changes

• #13519 3323f5c Thanks @​florian-lefebvre! - Refactors some internals to improve Rolldown compatibility

• #13545 a7aff41 Thanks @​stramel! - Prevent empty attributes from appearing in the SVG output

• #13552 9cd0fd4 Thanks @​ematipico! - Fixes an issue where Astro validated the i18n configuration incorrectly, causing false positives in downstream libraries.

astro@5.6.0

Minor Changes

• #13403 dcb9526 Thanks @​yurynix! - Adds a new optional prerenderedErrorPageFetch option in the Adapter API to allow adapters to provide custom implementations for fetching prerendered error pages.

  Now, adapters can override the default fetch() behavior, for example when fetch() is unavailable or when you cannot call the server from itself.

  The following example provides a custom fetch for 500.html and 404.html, reading them from disk instead of performing an HTTP call:

  return app.render(request, {
    prerenderedErrorPageFetch: async (url: string): Promise<Response> => {
      if (url.includes("/500")) {
          const content = await fs.promises.readFile("500.html", "utf-8");
          return new Response(content, {
            status: 500,
            headers: { "Content-Type": "text/html" },
          });
      }
      const content = await fs.promises.readFile("404.html", "utf-8");
        return new Response(content, {
          status: 404,
          headers: { "Content-Type": "text/html" },
        });
  });

  If no value is provided, Astro will fallback to its default behavior for fetching error pages.

  Read more about this feature in the Adapter API reference.

• #13482 ff257df Thanks @​florian-lefebvre! - Updates Astro config validation to also run for the Integration API. An error log will specify which integration is failing the validation.

  Now, Astro will first validate the user configuration, then validate the updated configuration after each integration astro:config:setup hook has run. This means updateConfig() calls will no longer accept invalid configuration.

  This fixes a situation where integrations could potentially update a project with a malformed configuration. These issues should now be caught and logged so that you can update your integration to only set valid configurations.

• #13405 21e7e80 Thanks @​Marocco2! - Adds a new eagerness option for prefetch() when using experimental.clientPrerender

  With the experimental clientPrerender flag enabled, you can use the eagerness option on prefetch() to suggest to the browser how eagerly it should prefetch/prerender link targets.

... (truncated)

Changelog

Sourced from astro's changelog.

5.6.1

Patch Changes

• #13519 3323f5c Thanks @​florian-lefebvre! - Refactors some internals to improve Rolldown compatibility

• #13545 a7aff41 Thanks @​stramel! - Prevent empty attributes from appearing in the SVG output

• #13552 9cd0fd4 Thanks @​ematipico! - Fixes an issue where Astro validated the i18n configuration incorrectly, causing false positives in downstream libraries.

5.6.0

Minor Changes

• #13403 dcb9526 Thanks @​yurynix! - Adds a new optional prerenderedErrorPageFetch option in the Adapter API to allow adapters to provide custom implementations for fetching prerendered error pages.

  Now, adapters can override the default fetch() behavior, for example when fetch() is unavailable or when you cannot call the server from itself.

  The following example provides a custom fetch for 500.html and 404.html, reading them from disk instead of performing an HTTP call:

  return app.render(request, {
    prerenderedErrorPageFetch: async (url: string): Promise<Response> => {
      if (url.includes("/500")) {
          const content = await fs.promises.readFile("500.html", "utf-8");
          return new Response(content, {
            status: 500,
            headers: { "Content-Type": "text/html" },
          });
      }
      const content = await fs.promises.readFile("404.html", "utf-8");
        return new Response(content, {
          status: 404,
          headers: { "Content-Type": "text/html" },
        });
  });

  If no value is provided, Astro will fallback to its default behavior for fetching error pages.

  Read more about this feature in the Adapter API reference.

• #13482 ff257df Thanks @​florian-lefebvre! - Updates Astro config validation to also run for the Integration API. An error log will specify which integration is failing the validation.

  Now, Astro will first validate the user configuration, then validate the updated configuration after each integration astro:config:setup hook has run. This means updateConfig() calls will no longer accept invalid configuration.

  This fixes a situation where integrations could potentially update a project with a malformed configuration. These issues should now be caught and logged so that you can update your integration to only set valid configurations.

• #13405 21e7e80 Thanks @​Marocco2! - Adds a new eagerness option for prefetch() when using experimental.clientPrerender

... (truncated)

Commits

• 9520a23 [ci] release (#13554)
• 5af40dc [ci] format
• 9cd0fd4 fix(i18n): incorrect validation (#13552)
• a7aff41 fix(svg): prevent empty attributes (#13545)
• 3323f5c feat: improve rolldown compatibility (#13519)
• 90b0ac1 [ci] release (#13540)
• d777420 Remove non-stable SVG features (#13488)
• f5a8b07 [ci] format
• c43bf8c feat: add session.load(id) method (#13539)
• 0edd79f [ci] format
• Additional commits viewable in compare view

Updates sharp from 0.33.5 to 0.34.0

Commits

• ddc1eb8 Release v0.34.0 (part 2 - see c26e67c)
• c26e67c Release v0.34.0
• a00ee26 Prevent glib assertions and checks #4351
• 6dfb60c Prevent prebuilt Linux sharp binaries from exporting symbols
• dbb7606 Prerelease v0.34.0-rc.1
• 031c808 Expose erode and dilate operations #4243
• 03e1b19 Allow wide-gamut HEIF output at higher bitdepths #4344
• 3e41f8b Non-animated GIF output defaults to no-loop #3394
• 3fd818c Prevent use of linux-x64 binaries with v1 microarchitecture
• d419aba Docs: add note about electron-forge and Webpack combo
• Additional commits viewable in compare view

Updates daisyui from 4.12.23 to 5.0.16

Release notes

Sourced from daisyui's releases.

v5.0.16

🌼 Read changelog: https://daisyui.com/docs/changelog/

📦 Install this update:

npm i -D daisyui@5.0.16

💚 Thank you for using daisyUI!

v5.0.15

🌼 Read changelog: https://daisyui.com/docs/changelog/

📦 Install this update:

npm i -D daisyui@5.0.15

💚 Thank you for using daisyUI!

v5.0.14

🌼 Read changelog: https://daisyui.com/docs/changelog/

📦 Install this update:

npm i -D daisyui@5.0.14

💚 Thank you for using daisyUI!

v5.0.13

🌼 Read changelog: https://daisyui.com/docs/changelog/

📦 Install this update:

npm i -D daisyui@5.0.13

💚 Thank you for using daisyUI!

v5.0.12

🌼 Read changelog: https://daisyui.com/docs/changelog/

📦 Install this update:

npm i -D daisyui@5.0.12

💚 Thank you for using daisyUI!

... (truncated)

Changelog

Sourced from daisyui's changelog.

5.0.16 (2025-04-07)

5.0.15 (2025-04-07)

5.0.14 (2025-04-07)

5.0.13 (2025-04-06)

Bug Fixes

• checkbox style inside tab-content. closes: #3753 (fe16212)

5.0.12 (2025-04-02)

Bug Fixes

• icon position of date input inside input wrapper on chromium-based (#3725) closes: #3708 (b1560a6)

5.0.11 (2025-04-02)

Bug Fixes

• card image-full radius color bleed. closes: #3734 (d6fb204)

5.0.10 (2025-04-02)

Bug Fixes

• :not(:has()) selectors getting prefix. closes: #3739 (771b6eb)

5.0.9 (2025-03-21)

Bug Fixes

• Join style on iOS. closes: #3691 (5afa08c)

5.0.8 (2025-03-21)

Bug Fixes

• alert unwanted gap if there's one child only. closes: #3702 (6d3eb06)

5.0.7 (2025-03-21)

... (truncated)

Commits

• edbcfce chore(release): 5.0.16
• 66c8a71 fix tabs-box render issue on Nuxt. closes: #3724
• 35f1650 fix: collapse-content transition duplicate, transition typo (#3761)
• 14b286b chore(release): 5.0.15
• bbf67d2 dropdown-center RTL, modal gutter, collapse-content animation
• 4b207ad chore(release): 5.0.14
• 387dead workaround for lightningcss issue of color mix in &:before. closes: #3758, ...
• ac1a45c chore(release): 5.0.13
• fe16212 fix: checkbox style inside tab-content. closes: #3753
• f59a004 chore(release): 5.0.12
• 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

[kjy5]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml