docs(telemetry): add 'How you are notified' section#3399
Draft
jacekradko wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
clerk/javascript#8549 replaced the postinstall telemetry notice in
@clerk/sharedwith a runtime notice gated to Node, non-CI, dev instances. Browser-only setups (@clerk/clerk-jsdirect, Vite SPAs on@clerk/clerk-reactwith no server, Chrome extensions) no longer get any in-band disclosure, so this page is now the authoritative one for them.Adds a short "How you are notified" section after the intro that spells out the server vs. browser split and restates the dev-instances-only fact. No changes to the
telemetryprop or opt-out instructions; existing partials and cross-links remain accurate as-is.