Migrate to VitePress, drop lyticus, bump tooling to LTS#155
Merged
Conversation
- Migrate VuePress 1 -> VitePress 1.6.4 (resolves 124 of 127 npm audit findings) - Drop lyticus analytics dependency - Bump @sentry/browser/integrations/tracing 7 -> @sentry/vue 10 (functional integrations API) - Bump prettier 2 -> 3, husky 8 -> 9, pretty-quick 3 -> 4 - Pin Node 24 (Active LTS) in .tool-versions and CI; bump actions/checkout + setup-node to v6 - Replace vuepress-plugin-sitemap with VitePress built-in sitemap; serve robots.txt from public/ - Rename README.md -> index.md to match VitePress home conventions - Move public assets to docs/public/ and rewrite markdown image paths - Tighten husky hook (drop deprecated husky.sh sourcing) and prepare script (husky 9 syntax) - Add local search; widen sidebar; replace deprecated apple-mobile-web-app-capable meta
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
npm auditfindings (the remaining 3 are moderate dev-server-only esbuild advisories trickling through Vite, no production impact).lyticusanalytics dependency (no replacement wired in).@sentry/browser+@sentry/integrations+@sentry/tracingv7 in favour of@sentry/vuev10 with the functional integrations API (browserTracingIntegration())._/husky.sh..tool-versionspinned to Node 24 (Active LTS); CI usesactions/checkout@v6+actions/setup-node@v6withnode-version: "24"and npm cache.vuepress-plugin-sitemapwith VitePress's built-insitemapconfig; replacedvuepress-plugin-robotswith a staticdocs/public/robots.txt; dropped@vuepress/plugin-back-to-top(default theme already has it).docs/README.md→docs/index.mdanddocs/setup/README.md→docs/setup/index.mdfor VitePress home conventions; moved public assets fromdocs/.vuepress/public/todocs/public/and rewrote markdown image paths from../.vuepress/public/Xto/X.apple-mobile-web-app-capablemeta withmobile-web-app-capable(kept the legacy one for older iOS Safari).npm run build/npm run devnow invokevitepress; the deploy script syncs fromdocs/.vitepress/dist.Verification
npm run buildis green (~5s, sitemap generated).npm auditafter the migration: 3 moderate (down from 127 — all dev-server esbuild only).createRoot), and the new SvelteKit page all render with correct sidebar, navigation, and code highlighting.Test plan
masterbefore that PR was open.npm run buildin CI and confirm a green deployment.documentation.formspark.io/sitemap.xmland/robots.txtresolve.