feat: add Vercel Analytics - #3
Merged
Merged
Conversation
Install @vercel/analytics and render <Analytics /> once at the App level so all routes (landing, editor, docs) are tracked without duplicating the component across early-return branches.
|
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.
Summary
@vercel/analyticspackage<Analytics />once at the App level insrc/App.jsxreturnso the analytics component is mounted once across all routes (landing, editor, docs)Test plan
npm run devand verify no console errors/), editor (#/editor), and docs (#/docs) — analytics component should persist across hash-based route changesnpm run buildand confirm production build completes without errors