chore(deps): bump the npm-deps group with 4 updates

[dependabot]

Bumps the npm-deps group with 4 updates: @astrojs/starlight, astro, @lavamoat/allow-scripts and prettier.

Updates @astrojs/starlight from 0.37.3 to 0.37.4

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.37.4

Patch Changes

• #3534 703fab0 Thanks @​HiDeoo! - Fixes support for running builds when npx is unavailable.

  Previously, Starlight would spawn a process to run the Pagefind search indexing binary using npx. On platforms where npx isn’t available, this could cause issues. Starlight now runs Pagefind using its Node.js API to avoid a separate process. As a side effect, you may notice that logging during builds is now less verbose.

• #3656 a0e6368 Thanks @​delucis! - Fixes several edge cases in highlighting the current page heading in Starlight’s table of contents

• #3663 00cbf00 Thanks @​lines-of-codes! - Adds Thai language support

• #3658 ac79329 Thanks @​delucis! - Avoids adding redundant aria-current="false" attributes to sidebar entries

• #3382 db295c2 Thanks @​trueberryless! - Fixes an issue where the mobile table of contents is unable to find the first heading when a page has a tall banner.

Changelog

Sourced from @​astrojs/starlight's changelog.

0.37.4

Patch Changes

• #3534 703fab0 Thanks @​HiDeoo! - Fixes support for running builds when npx is unavailable.

  Previously, Starlight would spawn a process to run the Pagefind search indexing binary using npx. On platforms where npx isn’t available, this could cause issues. Starlight now runs Pagefind using its Node.js API to avoid a separate process. As a side effect, you may notice that logging during builds is now less verbose.

• #3656 a0e6368 Thanks @​delucis! - Fixes several edge cases in highlighting the current page heading in Starlight’s table of contents

• #3663 00cbf00 Thanks @​lines-of-codes! - Adds Thai language support

• #3658 ac79329 Thanks @​delucis! - Avoids adding redundant aria-current="false" attributes to sidebar entries

• #3382 db295c2 Thanks @​trueberryless! - Fixes an issue where the mobile table of contents is unable to find the first heading when a page has a tall banner.

Commits

• 879d6b3 [ci] release (#3659)
• db295c2 fix: mobile toc issue with custom banners (#3382)
• a0e6368 Fix table of contents intersection observer (#3656)
• 703fab0 Pagefind CLI → Pagefind API (#3534)
• 42ff0aa [ci] format
• 00cbf00 i18n(th): Add Thai translations to Starlight UI (#3663)
• ac79329 Avoid adding redundant aria-current="false" to sidebar entries (#3658)
• See full diff in compare view

Updates astro from 5.16.11 to 5.16.15

Release notes

Sourced from astro's releases.

astro@5.16.15

Patch Changes

• #15286 0aafc83 Thanks @​florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

astro@5.16.14

Patch Changes

• #15213 c775fce Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Updates how the local provider must be used when using the experimental Fonts API

  Previously, there were 2 kinds of font providers: remote and local.

  Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

  -import { defineConfig } from "astro/config";
  +import { defineConfig, fontProviders } from "astro/config";
  export default defineConfig({
  experimental: {
  fonts: [{
  name: "Custom",
  cssVariable: "--font-custom",
  
  
         provider: "local",
  
  
  
  
  
         provider: fontProviders.local(),
  
  
  
         options: {
        variants: [
            {
                weight: 400,
                style: "normal",
                src: ["./src/assets/fonts/custom-400.woff2"]
            },
            {
                weight: 700,
                style: "normal",
                src: ["./src/assets/fonts/custom-700.woff2"]
            }
            // ...
        ]
  
  
  
         }
    }]
  
  }
  });

Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

See the experimental Fonts API docs for more information.

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.15

Patch Changes

• #15286 0aafc83 Thanks @​florian-lefebvre! - Fixes a case where font providers provided as class instances may not work when using the experimental Fonts API. It affected the local provider

5.16.14

Patch Changes

• #15213 c775fce Thanks @​florian-lefebvre! - BREAKING CHANGE to the experimental Fonts API only

  Updates how the local provider must be used when using the experimental Fonts API

  Previously, there were 2 kinds of font providers: remote and local.

  Font providers are now unified. If you are using the local provider, the process for configuring local fonts must be updated:

  -import { defineConfig } from "astro/config";
  +import { defineConfig, fontProviders } from "astro/config";
  export default defineConfig({
  experimental: {
  fonts: [{
  name: "Custom",
  cssVariable: "--font-custom",
  
  
         provider: "local",
  
  
  
  
  
         provider: fontProviders.local(),
  
  
  
         options: {
        variants: [
            {
                weight: 400,
                style: "normal",
                src: ["./src/assets/fonts/custom-400.woff2"]
            },
            {
                weight: 700,
                style: "normal",
                src: ["./src/assets/fonts/custom-700.woff2"]
            }
            // ...
        ]
  
  
  
         }
    }]
  
  }
  });

Once configured, there is no change to using local fonts in your project. However, you should inspect your deployed site to confirm that your new font configuration is being applied.

... (truncated)

Commits

• 8ca97e1 [ci] release (#15288)
• 0aafc83 fix(fonts): font providers as class instances (#15286)
• f7a8415 [ci] release (#15278)
• 7db2fda address sarah's feedback (#15280)
• c775fce feat(fonts)!: local provider unification (#15213)
• edabeaa fix(cli): add .vercel to .gitignore when using astro add vercel (#15185)
• ce0c346 [ci] release (#15270)
• 60d1045 clear fonts test cache (#15274)
• c4a15a8 [ci] format
• cb60ee1 feat(fonts): getFontBuffer() (#15182)
• Additional commits viewable in compare view

Updates @lavamoat/allow-scripts from 3.4.1 to 3.4.2

Release notes

Sourced from @​lavamoat/allow-scripts's releases.

allow-scripts: v3.4.2

3.4.2 (2026-01-20)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​lavamoat/aa bumped from ^4.3.4 to ^4.3.5

Changelog

Sourced from @​lavamoat/allow-scripts's changelog.

3.4.2 (2026-01-20)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​lavamoat/aa bumped from ^4.3.4 to ^4.3.5

Commits

• dedf3b1 chore: release main (#1873)
• See full diff in compare view

Updates prettier from 3.8.0 to 3.8.1

Release notes

Sourced from prettier's releases.

3.8.1

• Include available printers in plugin type declarations (#18706 by @​porada)

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.8.1

diff

Include available printers in plugin type declarations (#18706 by @​porada)

// Input
import * as prettierPluginEstree from "prettier/plugins/estree";
// Prettier 3.8.0
// Property 'printers' does not exist on type 'typeof import("prettier/plugins/estree")'. ts(2339)
prettierPluginEstree.printers.estree; //=> any
// Prettier 3.8.1
prettierPluginEstree.printers.estree; //=> Printer
prettierPluginEstree.printers["estree-json"]; //=> Printer

Commits

• 90983f4 Release 3.8.1
• 57f702f Include available printers in plugin type declarations (#18706)
• bece827 Revert change in release script
• 82a4ab2 Bump Prettier dependency to 3.8.0
• 5213ee4 Clean changelog_unreleased
• f95ad0f Comment out finished steps
• b2034e8 Fix release script
• 5824b15 Release 3.8.0
• 0433601 Add blog post for v3.8.0 (#18639)
• c45fef1 Fix LWC attribute with --embedded-language-formatting off (#18383)
• See full diff 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