fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/starlight (source)	0.25.5 -> 0.26.1
@types/node (source)	^20.14.15 -> ^20.15.0
esbuild	~0.23.0 -> ~0.23.1

---

Release Notes

withastro/starlight (@​astrojs/starlight)

v0.26.1

Compare Source

Patch Changes

• #​2219 74d4716 Thanks @​HiDeoo! - Fixes a sidebar persistence issue when navigating between pages with different sidebar content.

v0.26.0

Compare Source

Minor Changes

• #​1784 68f56a7 Thanks @​HiDeoo! - Adds <LinkButton> component for visually distinct and emphasized call to action links

• #​2150 9368494 Thanks @​delucis! - Adds state persistence across page navigations to the main site sidebar

• #​2087 caa84ea Thanks @​HiDeoo! - Adds persistence to synced <Tabs> so that a user's choices are reflected across page navigations.

• #​2051 ec3b579 Thanks @​HiDeoo! - Adds a guideline to the last step of the <Steps> component.

  If you want to preserve the previous behaviour and hide the guideline on final steps, you can add the following custom CSS to your site:

  /* Hide the guideline for the final step in <Steps> lists. */
  .sl-steps > li:last-of-type::after {
    background: transparent;
  }

• #​1784 68f56a7 Thanks @​HiDeoo! - Changes the hero component action button default variant from minimal to primary.

  ⚠️ BREAKING CHANGE: If you want to preserve the previous appearance, hero component action buttons previously declared without a variant will need to be updated to include the variant property with the value minimal.

  hero:
    actions:
      - text: View on GitHub
        link: https://github.com/astronaut/my-project
        icon: external
  +     variant: minimal

• #​2168 e044fee Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: Updates the <StarlightPage /> component sidebar prop to accept an array of SidebarItems like the main Starlight sidebar configuration in astro.config.mjs.

  This change simplifies the definition of sidebar items in the <StarlightPage /> component, allows for shared sidebar configuration between the global sidebar option and <StarlightPage /> component, and also enables the usage of autogenerated sidebar groups with the <StarlightPage /> component.
  If you are using the <StarlightPage /> component with a custom sidebar configuration, you will need to update the sidebar prop to an array of SidebarItem objects.

  For example, the following custom page with a custom sidebar configuration defines a “Resources” group with a “New” badge, a link to the “Showcase” page which is part of the docs content collection, and a link to the Starlight website:

evanw/esbuild (esbuild)

v0.23.1

Compare Source

• Allow using the node: import prefix with es* targets (#​3821)

  The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

  // Original code
  import fs from 'node:fs'
  fs.open
  
  // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "fs";
  fs.open;
  
  // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
  import fs from "node:fs";
  fs.open;

• Fix a panic when using the CLI with invalid build flags if --analyze is present (#​3834)

  Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

• Fix incorrect location of certain error messages (#​3845)

  This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

• Print comments before case clauses in switch statements (#​3838)

  With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

• Fix a memory leak with pluginData (#​3825)

  With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

---

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.