docs: add Vercel Analytics and Speed Insights to the VitePress site - #3
Merged
Merged
Conversation
Wire @vercel/analytics and @vercel/speed-insights into the docs theme via enhanceApp. Uses the framework-agnostic inject() / injectSpeedInsights() entrypoints rather than the @vercel/*/vue components: those declare a vue-router peer, and VitePress ships its own router. Both imports are dynamic and guarded by import.meta.env.SSR so nothing reaches the SSR pass of docs:build — they land in their own client chunks. Analytics picks up VitePress' pushState navigations by itself; Speed Insights does not, so its setRoute is chained onto router.onAfterRouteChange (chained, not replaced, to leave any existing handler intact). Both are devDependencies — docs-only, like vitepress itself. The zero-dependency guarantee is about `dependencies`, which stays absent. Data only flows once Web Analytics and Speed Insights are enabled on the Vercel project. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
1 participant
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.
Wire @vercel/analytics and @vercel/speed-insights into the docs theme via enhanceApp.
Uses the framework-agnostic inject() / injectSpeedInsights() entrypoints rather than the @vercel/*/vue components: those declare a vue-router peer, and VitePress ships its own router. Both imports are dynamic and guarded by import.meta.env.SSR so nothing reaches the SSR pass of docs:build — they land in their own client chunks.
Analytics picks up VitePress' pushState navigations by itself; Speed Insights does not, so its setRoute is chained onto router.onAfterRouteChange (chained, not replaced, to leave any existing handler intact).
Both are devDependencies — docs-only, like vitepress itself. The zero-dependency guarantee is about
dependencies, which stays absent.Data only flows once Web Analytics and Speed Insights are enabled on the Vercel project.