Update dependency typedoc to ^0.27.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typedoc (source)	^0.26.6 -> ^0.27.0

---

Release Notes

TypeStrong/TypeDoc (typedoc)

v0.27.1

Compare Source

Bug Fixes

• Include classes which inherit from another package in class hierarchy in packages mode, #​2467.
• Fixed handling of @categoryDescription and @groupDescription on module pages, #​2787.
• Fixed automatic discovery of entry points in packages mode.
• Reverted accidental style change for hierarchy page introduced in 0.27.0
• The hierarchy Expand/Collapse link will now only appear if the hierarchies are different.

v0.27.0

Compare Source

Breaking Changes

• Convert to ESM to enable easier use of ESM-only dependencies.
• Drop support for TypeScript <5.0, no longer supported by DefinitelyTyped
• Relaxed requirements for file names and generated url fragments. This may
  result in a different file name structure, #​2714.
• Anchors to document headings and reflections within a HTML generated pages
  have changed. They can be partially restored to the previous format by
  setting --sluggerConfiguration.lowercase false. This change was made to
  more closely match the default behavior of GitHub's markdown rendering and
  VSCode's autocomplete when creating a relative link to an external markdown
  file.
• Removed the hideParameterTypesInTitle option, this was originally added as
  a workaround for many signatures overflowing the available horizontal space
  in rendered pages. TypeDoc now has logic to wrap types/signatures smartly,
  so this option is no longer necessary.
• Changed the default kindSortOrder to put references last.
• Changed the default sort order to use alphabetical-ignoring-documents
  instead of alphabetical.
• Changed default of suppressCommentWarningsInDeclarationFiles to true
• API: Constructor signatures now use the parent class name as their name
  (e.g. X, not new X)
• API: @group, @category, @groupDescription and @categoryDescription
  will no longer be removed from the reflections they are present on. They are
  skipped during rendering with the notRenderedTags option.

Features

• Add support for TypeScript 5.7
• TypeDoc will now discover entry points from package.json exports if they
  are not provided manually, #​1937.
• Relative links to markdown files may now include #anchor links to
  reference a heading within them.
• Improved support for @param comments with nested object types, #​2555.
• Improved support for @param comments which reference a type
  alias/interface. Important properties on the referenced type can now be
  highlighted with @param options.foo, which will result in the additional
  note being included under the documentation for that parameter, #​2147. Note:
  This feature is limited to references. It is not supported on other types of
  types.
• Added a new outputs option which is an array of outputs. This can be used
  to render the documentation multiple times with different rendering options
  or output types, #​2597.
• Added support for rendering alerts (or callouts) in markdown.
• Add support for an @expand tag which can be placed on type aliases and
  interfaces. When a type with @expand is referenced and TypeDoc has a place
  to include additional details about the type, the properties of the type
  will be included in the page where @expand is found. Note that use of this
  tag can significantly increase the size of your generated documentation if
  it is applied to commonly used types as it will result in inlining the
  comments for those types everywhere they are referenced, #​2303.
• Add support for an @inline tag which can be placed on type aliases and
  interfaces. When a type with @inline is referenced, TypeDoc will resolve
  the referenced type and convert the type as if it was included directly
  within the referencing type. Note that use of this tag can significantly
  increase the size of your generated documentation if it is applied to
  commonly used types as it will result in inlining the comments for those
  types everywhere they are referenced, #​2303.
• Introduced a new @useDeclaredType tag for type aliases which can sometimes
  improve their documentation, #​2654..
• Added a new @mergeModuleWith tag which can be used to tell TypeDoc to
  place a module/namespace's children under a different module/namespace and
  remove the real parent, #​2281.
• Add notRenderedTags option. This option is similar to the excludeTags
  option, but while excludeTags will result in the tag being completely
  removed from the documentation, notRenderedTags only prevents it from
  being included when rendering.
• Added groupReferencesByType option.
• Added navigation.excludeReferences option
• Added useFirstParagraphOfCommentAsSummary option to configure how TypeDoc
  handles comments for module members without the @summary tag.
• Introduced favicon option to specify a .ico or .svg favicon to reference.
• Sections within the page and in the "On This Page" navigation are now tied
  together and will expand/collapse together, #​2335.
• API: Introduced a new app.outputs object for defining new output strategies.
• API: TypeDoc's CSS is now wrapped in @layer typedoc, #​2782.

Bug Fixes

• TypeDoc now properly flags readonly index signatures.
• TypeDoc will now use the first signature's comment for later signatures in
  overloads if present, #​2718.
• Fixed handling of @enum if the type was declared before the variable, #​2719.
• Fixed empty top level modules page in packages mode, #​2753.
• TypeDoc can now link to type alias properties, #​2524.
• TypeDoc will now document the merged symbol type when considering globals
  declared inside declare global, #​2774
• TypeDoc now converts declare module "foo" as a module rather than a namespace, #​2778.
• Import types in type aliases now use module member references if present, #​2779.
• Fixed an issue where properties were not properly marked optional in some
  cases. This primarily affected destructured parameters.
• Added yaml to the highlight languages supported by default.
• TypeDoc now recognizes txt as an alias of text to indicate a code block
  should not be highlighted.
• Items which are hidden with @ignore or @hidden but still referenced by
  other types will no longer produce warnings about not being exported.
• If a project only has one module within it, TypeDoc will now consider that
  module when resolving @link tags.
• The arrows to indicate whether or not a section is open now work when
  JavaScript is disabled.
• Group/category search boosts are now applied when writing the search index
  rather than when converting. This prevents issues where boosts used by just
  one package were incorrectly reported as unused when running with
  entryPointStrategy set to packages.

Thanks!

• @​Huxpro
• @​mrfigg
• @​tgreyuk
• @​XeroAlpha

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: typedoc-plugin-markdown@4.2.10
npm error Found: typedoc@0.27.1
npm error node_modules/typedoc
npm error   dev typedoc@"^0.27.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typedoc@"0.26.x" from typedoc-plugin-markdown@4.2.10
npm error node_modules/typedoc-plugin-markdown
npm error   dev typedoc-plugin-markdown@"^4.2.6" from the root project
npm error
npm error Conflicting peer dependency: typedoc@0.26.11
npm error node_modules/typedoc
npm error   peer typedoc@"0.26.x" from typedoc-plugin-markdown@4.2.10
npm error   node_modules/typedoc-plugin-markdown
npm error     dev typedoc-plugin-markdown@"^4.2.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-11-28T10_06_16_886Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-28T10_06_16_886Z-debug-0.log