Add browser profiling to profiling getting started #7665
Merged
Conversation
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@AbhiPrasad thank you! Yes, I have been somewhat intentionally quiet on this as I'm trying to gather feedback from folks using it before I add it to all of our docs. |
AbhiPrasad
commented
Aug 17, 2023
|
Updated so it now says |
adinauer
pushed a commit
that referenced
this pull request
Aug 18, 2023
* Add browser profiling to profiling getting started * Update src/docs/product/profiling/getting-started.mdx
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Noticed this when clicking docs link in https://blog.sentry.io/profiling-to-speed-up-your-apps/ but didn't see browser profiling 😢.
I wonder if we should add custom instructions for Next.js (setting it up for both server and client)