Last 12 weeks · 27 commits
4 of 6 standards met
Fixes #3966 Summary This PR fixes: Unified API for VitePress Plugins Changes Testing Please review the changes carefully. The fix was verified against the existing test suite. This PR was created with the assistance of Claude Haiku 4.5 by Anthropic | effort: low. Happy to make any adjustments!* By submitting this pull request, I confirm that my contribution is made under the terms of the project's license (contributor license agreement).
Description This PR adds support for synchronizing multiple code groups using a shared key. The syntax is as follows: Here, is the key used to link the groups. The documentation has been updated accordingly, and an example has been added. Linked Issues fixes #2954 Additional Context I've also update vitepress website to use this in getting-started.
Repository: vuejs/vitepress. Description: Vite & Vue powered static site generator. Stars: 17181, Forks: 2671. Primary language: TypeScript. Languages: TypeScript (57.2%), Vue (30.1%), CSS (11.4%), JavaScript (1.3%). License: MIT. Homepage: https://vitepress.dev Topics: docs-generator, hacktoberfest, markdown, ssg, vite, vue. Latest release: v2.0.0-alpha.16 (4w ago). Open PRs: 100, open issues: 385. Last activity: 3d ago. Community health: 62%. Top contributors: brc-dd, yyx990803, kiaking, zonemeen, posva, antfu, userquin, meteorlxy, CHOYSEN, dependabot[bot] and others.
TypeScript
Description include all regions with the same name, not just the first one when a file does not contain the region, don't include it entirely, rather warn that the region was not found add option to strip all #region comments from the included snippet Rationale VitePress supports including a part of a file through a VS Code region. However, when multiple regions have the same name, only one is included. The workaround plugin suggested in #3690 is no longer maintained. [^1] Furthermore, it suffers from a memory leak causing huge RAM usage. [^2] While we at Fabric Docs have forked the plugin [^3] to fix some issues, it still feels fragile. Another problem is having to use two different syntaxes (` [^2]: via [^3]:
Description Add mode for supporting light mode only. Linked Issues #4471 Additional Context My design system supports light theme, but the color palette that I'm using supports both light and dark theme. \ So with appearance, it breaks my color palette. [!TIP] The author of this PR can publish a _preview release_ by commenting below.
Description Add created time to doc footer. Linked Issues close #4892 close #1891 Additional Context This feature was previously requested in 2023 but remains unimplemented. issue #1891 pull #1956 pull #1964 [!TIP] The author of this PR can publish a _preview release_ by commenting below.
I'm using , which is quite an important feature I think. But when I try to define typed routes, I basically failed. Litteraly no where mentions about the usage of . I have to find how to define a typed dynamic routes from looking at the test code. With knowing the answer now, let's see the google result