[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vitepress-sidebar (source)	1.40.0 → 1.41.0

---

Release Notes

jooy2/vitepress-sidebar (vitepress-sidebar)

v1.41.0

Compare Source

• Add removePrefixFromLink option, which removes the prefix from the links of the sidebar the way removePrefixAfterOrdering removes it from the titles. 1.guide/2.setup.md is linked as /guide/setup once the items have been ordered by the prefix, and prefixSeparator decides where the prefix ends. withSidebar also adds the rewrites that serve every page below the scanned folder at that path, after the rewrites of the VitePress configuration when they are a function; rewrites written as an object cannot be combined with it and are reported. generateSidebar cannot add them, so the rewrite has to be written by hand there. A $folder.link is used as written, and two pages of the sidebar that end up at the same path are reported with a warning. (#​222)
• Add splitSidebarByFolder option, which gives every folder a sidebar of its own instead of a collapsible group, from a single set of options. A folder is opened through the link it has in the sidebar above, and the root group of its sidebar links back to that sidebar. splitSidebarRootGroupText names the group, and is ◀ :title unless it is set, where :title is the title of the folder. excludeByFolderDepth decides how deep each sidebar goes and is 2 unless it is set, and useFolderLinkFromIndexFile is true unless it is set, so that a folder links to its index.md. A folder without a link of its own opens on the first page of its sidebar, and one that holds no page at all is left out. A sidebar passed for the path of a folder is used instead of the one the split would make there. (#​174)
• includeDynamicRoutes now works on VitePress 2. Its resolvePages no longer takes a source directory and returns the pages it found; it takes a site configuration and fills the pages into it instead. The old call raised a TypeError that was caught and reported as a loader failure, so every page generated by a dynamic route was dropped from the sidebar with nothing but a warning to explain it. The call is now chosen from the major version of the VitePress the project has installed, and both majors are covered by the test suite.
• The pages of a dynamic route are ordered by their path on VitePress 2, instead of in the order the paths loader returned them. VitePress 2 sorts them before handing them over and does not expose the original order, so a project that relied on the order of its paths loader has to state the order it wants, with an order parameter and sortMenusByFrontmatterOrder. Nothing changes on VitePress 1.
• A link that is not relative to the base of its sidebar is now kept as it is written in multiple sidebars. VitePress puts the base in front of every link of a sidebar, so rootGroupLink: '/' became //, which VitePress opens as another host, and a $folder.link of /guide/start in a sidebar based at /guide/ became /guide//guide/start. Such a sidebar is now returned with its relative links resolved against basePath or resolvePath, and with an empty base. A relative link is resolved against the base as before.
• A problem found in a sidebar.config.json is now reported once per build. Every sidebar reads the configuration files above the folder it scans, so with several sidebars the same warning was printed once for each of them. A $folder in the folder a sidebar starts its scan from is no longer reported either, because that folder is still an item of a sidebar that scans the folder above it. Only a $folder at or above the document root, which no sidebar shows, is reported.
• documentRootPath in a sidebar.config.json below the document root is now ignored with a warning, as the documentation says, also in the folder a sidebar starts its scan from. A file on the way down to scanStartPath replaced the document root the scan was built from, so the build stopped because the path to scan did not exist.
• Every version is now published to npm from GitHub Actions with a provenance statement, which ties the package to the commit and the workflow that built it. Each version also gets a tag and a GitHub release whose notes are its section of this changelog.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

🔕 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.