-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
docs(learn): improve debugging docs #8329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(learn): improve debugging docs #8329
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the debugging documentation to improve clarity and organization of the DevTools connection instructions, and modernizes several external reference links.
- Restructured Chrome/Edge DevTools instructions into two distinct options with clearer step-by-step guidance
- Updated external documentation links to more specific and current resources
- Removed the Gitpod section from the debugging tools list
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <[email protected]> Signed-off-by: Efe <[email protected]>
|
LGTM, thanks |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8329 +/- ##
==========================================
- Coverage 76.72% 76.67% -0.06%
==========================================
Files 118 118
Lines 9805 9805
Branches 335 336 +1
==========================================
- Hits 7523 7518 -5
- Misses 2280 2285 +5
Partials 2 2 ☔ View full report in Codecov by Sentry. |
Description
I first just wanted to replace the outdated Microsoft Edge link with the correct DevTools doc, but it looks like the debugging section overall is out of date. This PR aims to improve the docs a bit (at least partially)
Would it make sense to expand this into a broader rework later?
Validation
Related Issues
Check List
pnpm formatto ensure the code follows the style guide.pnpm testto check if all tests are passing.pnpm buildto check if the website builds without errors.