-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
docs(js): React Quick Start guide for Error Monitoring feature only #13061
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Bundle ReportChanges will increase total bundle size by 756 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-server-cjsAssets Changed:
|
| Sentry should be initialized as early as possible in your application. We recommend putting the Sentry initialization code into its own file and including that file as the first import in your application entry point as shown in the example below: | ||
| ### Initialize the Sentry SDK | ||
|
|
||
| To import and initialize Sentry, create a file, for example, `instrument.js`, in your project and add the following code: |
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.
| To import and initialize Sentry, create a file, for example, `instrument.js`, in your project and add the following code: | |
| To import and initialize Sentry, create a file in your project's root directory, for example, `instrument.js`, in your project and add the following code: |
coolguyzone
left a comment
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.
This is looking great!
chargome
left a comment
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.
Nice change! But we need to resolve the TOC issue before as that is rather confusing in the current state
| </Alert> | ||
|
|
||
| <OnboardingOption optionId="performance"> | ||
| ## Step 4: Set Up React Router |
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.
this one is optional
…ick-start/react-manual
|
@mydea Now that the ToC is resolved, we can move on with this one -- Alex and Charly have already reviewed it. |
mydea
left a comment
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.
left one tiny suggestion, other than this looks great!
Co-authored-by: Francesco Gringl-Novy <[email protected]>
DESCRIBE YOUR PR
Rework the Node.js Getting Started page into a Quick Start guide.
I also created some includes for reusable content and updated existing guides to use these includes -> let me know if you'd prefer we do this in a separate PR!
Note: I've only changed content that is relevant for Issues/Error Monitoring. We'll rework Tracing & Session Replay in a future PR.
Belongs to: #12991
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
EXTRA RESOURCES