chore(deps): bump the minor-and-patch group with 6 updates

[dependabot]

Bumps the minor-and-patch group with 6 updates:

Package	From	To
astro	5.4.2	5.5.2
typedoc	0.27.9	0.28.0
typedoc-plugin-markdown	4.4.2	4.5.0
@eslint-react/eslint-plugin	1.31.0	1.34.1
typescript-eslint	8.26.0	8.26.1
vite	6.2.1	6.2.2

Updates astro from 5.4.2 to 5.5.2

Release notes

Sourced from astro's releases.

astro@5.5.2

Patch Changes

• #13415 be866a1 Thanks @​ascorbic! - Reuses experimental session storage object between requests. This prevents memory leaks and improves performance for drivers that open persistent connections to a database.

• #13420 2f039b9 Thanks @​ematipico! - It fixes an issue that caused some regressions in how styles are bundled.

astro@5.5.1

Patch Changes

• #13413 65903c9 Thanks @​ascorbic! - Makes experimental flag optional

astro@5.5.0

Minor Changes

• #13402 3e7b498 Thanks @​ematipico! - Adds a new experimental flag called experimental.preserveScriptOrder that renders <script> and <style> tags in the same order as they are defined.

  When rendering multiple <style> and <script> tags on the same page, Astro currently reverses their order in your generated HTML output. This can give unexpected results, for example CSS styles being overridden by earlier defined style tags when your site is built.

  With the new preserveScriptOrder flag enabled, Astro will generate the styles in the order they are defined:

  import { defineConfig } from 'astro/config';
  export default defineConfig({
  experimental: {
  preserveScriptOrder: true,
  },
  });

  For example, the following component has two <style> tags, and both define the same style for the body tag:

  <p>I am a component</p>
  <style>
    body {
      background: red;
    }
  </style>
  <style>
    body {
      background: yellow;
    }
  </style>

  Once the project is compiled, Astro will create an inline style where yellow appears first, and then red. Ultimately, the red background is applied:

... (truncated)

Changelog

Sourced from astro's changelog.

5.5.2

Patch Changes

• #13415 be866a1 Thanks @​ascorbic! - Reuses experimental session storage object between requests. This prevents memory leaks and improves performance for drivers that open persistent connections to a database.

• #13420 2f039b9 Thanks @​ematipico! - It fixes an issue that caused some regressions in how styles are bundled.

5.5.1

Patch Changes

• #13413 65903c9 Thanks @​ascorbic! - Makes experimental flag optional

5.5.0

Minor Changes

• #13402 3e7b498 Thanks @​ematipico! - Adds a new experimental flag called experimental.preserveScriptOrder that renders <script> and <style> tags in the same order as they are defined.

  When rendering multiple <style> and <script> tags on the same page, Astro currently reverses their order in your generated HTML output. This can give unexpected results, for example CSS styles being overridden by earlier defined style tags when your site is built.

  With the new preserveScriptOrder flag enabled, Astro will generate the styles in the order they are defined:

  import { defineConfig } from 'astro/config';
  export default defineConfig({
  experimental: {
  preserveScriptOrder: true,
  },
  });

  For example, the following component has two <style> tags, and both define the same style for the body tag:

  <p>I am a component</p>
  <style>
    body {
      background: red;
    }
  </style>
  <style>
    body {
      background: yellow;
    }
  </style>

... (truncated)

Commits

• 61b7154 [ci] release (#13418)
• 2f039b9 Revert "Replace internal cssScopeTo implementation to vite.cssScopeTo" (#13420)
• be866a1 fix: reuse storage objects in sessions (#13415)
• 118d3e1 [ci] release (#13414)
• 65903c9 fix: make preserveScriptOrder an optional flag (#13413)
• 4277225 [ci] release (#13397)
• 3b5196d [ci] format
• fd70537 chore: breakdown changelog (#13410)
• fb6859a docs: fix formatting of excludeLangs default value (#13408)
• 0efdc22 fix: rethrow astroerrors in image processing (#13407)
• Additional commits viewable in compare view

Updates typedoc from 0.27.9 to 0.28.0

Release notes

Sourced from typedoc's releases.

v0.28.0

Breaking Changes

• TypeDoc now expects all input globs paths to be specified with / path separators, #2825.
• TypeDoc's --entryPointStrategy merge mode now requires JSON from at least version 0.28.0.
• Removed jp translations from lang, to migrate switch to ja.
• File name references in intentionallyNotExported now use a package name/package relative path instead of an absolute path for matching.
• The source-order sort ordering now considers package names / package relative paths instead of using the absolute paths to a file.
• TypeDoc will only check for a project README file next to the discovered package.json file if --readme is not set this change improves handling of monorepo setups where some packages have readme files and others do not, #2875.
• Function-like variable exports will now only be automatically converted as function types if they are initialized with a function expression. TypeDoc can be instructed to convert them as functions with the @function tag, #2881.
• Object literal type alias types will now be converted in a way which causes them to be rendered more similarly to how interfaces are rendered, #2817.

API Breaking Changes

• ProjectReflection.getReflectionFromSymbol and ProjectReflection.getSymbolFromReflection have been moved to Context
• Path and PathArray parameter types now always contain normalized paths.
• Introduced a Router which is used for URL creation. Reflection.url, Reflection.anchor, and Reflection.hasOwnDocument have been removed.
• Deserializer.reviveProject(s) no longer accepts an option to add project documents.
• Deserializer.reviveProjects now requires an alwaysCreateEntryPointModule option.
• Comment.serializeDisplayParts no longer requires a serializer argument.
• ReflectionSymbolId.fileName is now optional, TypeDoc now stores a combination of a package name and package relative path instead. The fileName property will be present when initially created, but is not serialized.
• Removed DeclarationReflection.relevanceBoost attribute which was added for plugins, but never used.
• i18n proxy is no longer passed to many functions, instead, reference i18n exported from the module directly.
• ReflectionKind.singularString and ReflectionKind.pluralString now returns translated strings. The methods on Internationalization to do this previously have been removed.
• The HTML output structure for the search box has changed to support the new modal.
• DefaultThemeRenderContext's typeDeclaration and typeDetailsIfUseful methods now require both a reflection and a type in order to support @expandType

Features

• Add support for TypeScript 5.8.x
• The search modal in the HTML output has been rewritten to provide better mobile support
• Added a --router option which can be used to modify TypeDoc's output folder structure. This can be extended with plugins, #2111.
• Introduced the @primaryExport modifier tag to provide more fine grained control over export conversion order, #2856
• Introduced packagesRequiringDocumentation option for validation.notDocumented, TypeDoc will expect comments to be present for symbols in the specified packages.
• TypeDoc now exports a typedoc/browser entrypoint for parsing and using serialized JSON files, #2528.
• Type packageOptions as Partial<TypeDocOptions>, #2878.
• TypeDoc will now warn if an option which should only be set at the root level is set in packageOptions, #2878.
• Introduced @function tag to force TypeDoc to convert variable declarations with a type annotation as functions, #2881.

... (truncated)

Changelog

Sourced from typedoc's changelog.

v0.28.0 (2025-03-15)

Breaking Changes

• TypeDoc now expects all input globs paths to be specified with / path separators, #2825.
• TypeDoc's --entryPointStrategy merge mode now requires JSON from at least version 0.28.0.
• Removed jp translations from lang, to migrate switch to ja.
• File name references in intentionallyNotExported now use a package name/package relative path instead of an absolute path for matching.
• The source-order sort ordering now considers package names / package relative paths instead of using the absolute paths to a file.
• TypeDoc will only check for a project README file next to the discovered package.json file if --readme is not set this change improves handling of monorepo setups where some packages have readme files and others do not, #2875.
• Function-like variable exports will now only be automatically converted as function types if they are initialized with a function expression. TypeDoc can be instructed to convert them as functions with the @function tag, #2881.
• Object literal type alias types will now be converted in a way which causes them to be rendered more similarly to how interfaces are rendered, #2817.

API Breaking Changes

• ProjectReflection.getReflectionFromSymbol and ProjectReflection.getSymbolFromReflection have been moved to Context
• Path and PathArray parameter types now always contain normalized paths.
• Introduced a Router which is used for URL creation. Reflection.url, Reflection.anchor, and Reflection.hasOwnDocument have been removed.
• Deserializer.reviveProject(s) no longer accepts an option to add project documents.
• Deserializer.reviveProjects now requires an alwaysCreateEntryPointModule option.
• Comment.serializeDisplayParts no longer requires a serializer argument.
• ReflectionSymbolId.fileName is now optional, TypeDoc now stores a combination of a package name and package relative path instead. The fileName property will be present when initially created, but is not serialized.
• Removed DeclarationReflection.relevanceBoost attribute which was added for plugins, but never used.
• i18n proxy is no longer passed to many functions, instead, reference i18n exported from the module directly.
• ReflectionKind.singularString and ReflectionKind.pluralString now returns translated strings. The methods on Internationalization to do this previously have been removed.
• The HTML output structure for the search box has changed to support the new modal.
• DefaultThemeRenderContext's typeDeclaration and typeDetailsIfUseful methods now require both a reflection and a type in order to support @expandType

Features

• Add support for TypeScript 5.8.x
• The search modal in the HTML output has been rewritten to provide better mobile support
• Added a --router option which can be used to modify TypeDoc's output folder structure. This can be extended with plugins, #2111.
• Introduced the @primaryExport modifier tag to provide more fine grained control over export conversion order, #2856
• Introduced packagesRequiringDocumentation option for validation.notDocumented, TypeDoc will expect comments to be present for symbols in the specified packages.
• TypeDoc now exports a typedoc/browser entrypoint for parsing and using serialized JSON files, #2528.
• Type packageOptions as Partial<TypeDocOptions>, #2878.
• TypeDoc will now warn if an option which should only be set at the root level is set in packageOptions, #2878.
• Introduced @function tag to force TypeDoc to convert variable declarations with a type annotation as functions, #2881.

... (truncated)

Commits

• 28f6d63 Update changelog for release
• 9ed2e6f Bump version to 0.28, upgrade deps
• de7f969 Fix rendering of index headings
• 4c2712f Export new types
• 97de828 Update changelog pre-release
• 0f339fa Update changelog
• ceedb73 Merge branch 'beta'
• 5eaa109 Merge pull request #2894 from crimx/patch-1
• f5d676e Make rendering types more lax
• 309a07c Fix formatting of functions within types
• Additional commits viewable in compare view

Updates typedoc-plugin-markdown from 4.4.2 to 4.5.0

Release notes

Sourced from typedoc-plugin-markdown's releases.

typedoc-plugin-markdown@4.5.0

Minor Changes

• Implemented custom routers for plugin to support TypeDoc 0.28 router implementation.
• Added "typeAliasPropertiesFormat" option to support TypeDoc 0.28 updated behaviour for Object literal type alias types.

Patch Changes

• Mark object properties as optional in PluginOptions interface (#777).

Changelog

Sourced from typedoc-plugin-markdown's changelog.

4.5.0 (2025-03-16)

This release introduces support for TypeDoc 0.28 that contains several under-the-hood breaking API changes.

From a consumer perspective there should be no direct breaking change from the plugin itself, but there are some architectural and output structure changes to consider.

Architectural Changes

• This plugin now utilizes TypeDoc's router feature. This implementation replaces the now deprecated "outputFileStrategy" option. "outputFileStrategy" is still supported for now, but will now point to the "kind-structure" and "module" router keys respectively. Further details are contained in the documentation website.
• Please note that separate strategies for output generation in different packages (when entryPointStrategy=packages) is no longer possible with this new architecture.

Structural Changes

• As per TypeDoc model updates, Object literal Type Alias members are now rendered in groups ("Properties", "Methods") etc rather than under a single "Type Declaration" heading.
• A new option "typeAliasPropertiesFormat" has been exposed to place properties rendered from the updated structure to a table format.
• Type parameter list views have been updated to separate items with markdown headings for consistency and to improve readability when parameters have detailed explanations or complex properties. If type parameters are straightforward and few in number switching to typeParametersFormat=table might be preferable.

Minor Changes

• Implemented custom routers for plugin to support TypeDoc 0.28 router implementation.
• Added "typeAliasPropertiesFormat" option to support TypeDoc 0.28 updated behaviour for Object literal type alias types.

Patch Changes

• Mark object properties as optional in PluginOptions interface (#777).

Commits

• e4bf064 Version Packages
• ec572d4 feat(core): typedoc 0.28 compatibility fixes and enhancements
• c50eb66 chore(all): fix models script
• 93e43a2 docs(all): updated dev docs
• 1000c9c fix(core): updated changelog date
• See full diff in compare view

Updates @eslint-react/eslint-plugin from 1.31.0 to 1.34.1

Release notes

Sourced from @​eslint-react/eslint-plugin's releases.

v1.34.1 (2025-03-15)

What's Changed

🐞 Fixes

• fix: false positive in react-x/no-context-provider on symbols named Provider which are imported from third-party libs, closes #991 by @​Rel1cx in Rel1cx/eslint-react#992

Full Changelog: Rel1cx/eslint-react@v1.34.0...v1.34.1

v1.34.0 (2025-03-15)

What's Changed

🪄 Improvements

• refactor: export the create function of each rule by @​Rel1cx in Rel1cx/eslint-react#989
• refactor(plugins/x): rename no-nested-components rule to no-nested-component-definitions and update related docs by @​Rel1cx in Rel1cx/eslint-react#990

📝 Changes you should be aware of

The following rules have been renamed:

• react-x/no-nested-components to react-x/no-nested-component-definitions
• @eslint-react/no-nested-components to @eslint-react/no-nested-component-definitions

The old rule names will still be available until the next major update to avoid breaking changes.

Full Changelog: Rel1cx/eslint-react@v1.33.0...v1.34.0

v1.33.0 (2025-03-14)

What's Changed

🐞 Fixes

• fix: update rule severity for no-flush-sync and no-void-elements-with-children in recommended presets by @​Rel1cx in Rel1cx/eslint-react#988

🪄 Improvements

• refactor(plugins/x): rename ensure-forward-ref-using-ref to no-useless-forward-ref by @​Rel1cx in Rel1cx/eslint-react#987

📝 Changes you should be aware of

The following rules have been renamed:

• react-x/ensure-forward-ref-using-ref to react-x/no-useless-forward-ref
• @eslint-react/ensure-forward-ref-using-ref to @eslint-react/no-useless-forward-ref

The old rule names will still be available until the next major update to avoid breaking changes.

Full Changelog: Rel1cx/eslint-react@v1.32.1...v1.33.0

v1.32.1 (2025-03-13)

... (truncated)

Changelog

Sourced from @​eslint-react/eslint-plugin's changelog.

v1.34.1 (2025-03-15)

🐞 Fixes

• fix: false positive in react-x/no-context-provider on symbols named Provider which are imported from third-party libs, closes #991 by @​Rel1cx in Rel1cx/eslint-react#992

Full Changelog: Rel1cx/eslint-react@v1.34.0...v1.34.1

v1.34.0 (2025-03-15)

🪄 Improvements

• refactor: export the create function of each rule by @​Rel1cx in Rel1cx/eslint-react#989
• refactor(plugins/x): rename no-nested-components rule to no-nested-component-definitions and update related docs by @​Rel1cx in Rel1cx/eslint-react#990

📝 Changes you should be aware of

The following rules have been renamed:

• react-x/no-nested-components to react-x/no-nested-component-definitions
• @eslint-react/no-nested-components to @eslint-react/no-nested-component-definitions

The old rule names will still be available until the next major update to avoid breaking changes.

Full Changelog: Rel1cx/eslint-react@v1.33.0...v1.34.0

v1.33.0 (2025-03-14)

🐞 Fixes

• fix: update rule severity for no-flush-sync and no-void-elements-with-children in recommended presets by @​Rel1cx in Rel1cx/eslint-react#988

🪄 Improvements

• refactor(plugins/x): rename ensure-forward-ref-using-ref to no-useless-forward-ref by @​Rel1cx in Rel1cx/eslint-react#987

📝 Changes you should be aware of

The following rules have been renamed:

• react-x/ensure-forward-ref-using-ref to react-x/no-useless-forward-ref
• @eslint-react/ensure-forward-ref-using-ref to @eslint-react/no-useless-forward-ref

The old rule names will still be available until the next major update to avoid breaking changes.

Full Changelog: Rel1cx/eslint-react@v1.32.1...v1.33.0

v1.32.1 (2025-03-13)

🐞 Fixes

... (truncated)

Commits

• 526fa95 release: 1.34.1
• f20fb84 release: 1.34.1-beta.1
• 651bb76 release: 1.34.1-next.1
• 25dc8ff fix: false positive in 'react-x/no-context-provider' on components named 'Pro...
• 2f605cf release: 1.34.0
• e68dae7 release: 1.34.0-beta.2
• d39254b release: 1.34.0-next.2
• b0013ee refactor: rename no-nested-components rule to `no-nested-component-definiti...
• c6512b1 release: 1.34.0-beta.1
• 6e5b96e release: 1.34.0-next.1
• Additional commits viewable in compare view

Updates typescript-eslint from 8.26.0 to 8.26.1

Release notes

Sourced from typescript-eslint's releases.

v8.26.1

8.26.1 (2025-03-10)

🩹 Fixes

• eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as eligible for nullish coalescing (#10865)
• eslint-plugin: [no-unsafe-return] handle recursive type (#10883)
• rule-tester: export TestLanguageOptions (#10930)

❤️ Thank You

• Dave @​reduckted
• Kirk Waiblinger @​kirkwaiblinger
• YeonJuan @​yeonjuan

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from typescript-eslint's changelog.

8.26.1 (2025-03-10)

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Commits

• 9aa0b6b chore(release): publish 8.26.1
• See full diff in compare view

Updates vite from 6.2.1 to 6.2.2

Release notes

Sourced from vite's releases.

v6.2.2

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

6.2.2 (2025-03-14)

• fix: await client buildStart on top level buildStart (#19624) (b31faab), closes #19624
• fix(css): inline css correctly for double quote use strict (#19590) (d0aa833), closes #19590
• fix(deps): update all non-major dependencies (#19613) (363d691), closes #19613
• fix(indexHtml): ensure correct URL when querying module graph (#19601) (dc5395a), closes #19601
• fix(preview): use preview https config, not server (#19633) (98b3160), closes #19633
• fix(ssr): use optional chaining to prevent "undefined is not an object" happening in `ssrRewriteStac (4309755), closes #19612
• feat: show friendly error for malformed base (#19616) (2476391), closes #19616
• feat(worker): show asset filename conflict warning (#19591) (367d968), closes #19591
• chore: extend commit hash correctly when ambigious with a non-commit object (#19600) (89a6287), closes #19600

Commits

• b12911e release: v6.2.2
• 98b3160 fix(preview): use preview https config, not server (#19633)
• b31faab fix: await client buildStart on top level buildStart (#19624)
• dc5395a fix(indexHtml): ensure correct URL when querying module graph (#19601)
• 2476391 feat: show friendly error for malformed base (#19616)
• 4309755 fix(ssr): use optional chaining to prevent "undefined is not an object" happe...
• 363d691 fix(deps): update all non-major dependencies (#19613)
• d0aa833 fix(css): inline css correctly for double quote use strict (#19590)
• 367d968 feat(worker): show asset filename conflict warning (#19591)
• 89a6287 chore: extend commit hash correctly when ambigious with a non-commit object (...
• 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

[lawvs]

Related to typedoc2md/typedoc-plugin-markdown#788

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.