Expose the Sentry Error Id on the error page
Nobody has claimed this yet.
- Dominant language
- Svelte
- Stars
- 1.2k
- Forks
- 515
- Avg merge
- 23h
- Merged PRs (30d)
- 13
Description
Would be funny to make our error page say something like:
Oopsie Dasiy. We had an error.
Don't worry, we boxed it up and gave it a name. Your error is little baby 4sd4sdf234k2l3j4 and we're rushing to the tend to it right now.
THEN if we can make the syntax site errors public and link to it? is that possible?
I did some early look into it and the sentry captureException API returns the ID. The Sveltekit lib doesn't return the ID, so we would either need to change that, or just re-implment the handlerError function here: https://github.com/getsentry/sentry-javascript/blob/develop/packages/sveltekit/src/server/handleError.ts#L24
cc @benvinegar for ideas on this
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the SvelteKit handleError implementation linked in the issue and checking how Sentry's captureException API returns an ID. Determine whether the existing SvelteKit integration can expose that ID or whether the handler must be reimplemented. Done means the error page displays the Sentry error ID and the feasibility of public syntax-site error links is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- observability-sre, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100