yashdev9274 / yashdev9274/supercli
Set up Sentry error tracking and performance monitoring
Open
Nobody has claimed this yet.
infrastructure
- Dominant language
- TypeScript
- Stars
- 214
- Forks
- 41
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 34
Description
Description
Integrate Sentry for monitoring errors and performance in production.
Expected Deliverables
- Install and configure @sentry/nextjs
- Set up environment variables for Sentry DSN
- Create custom error boundary using Sentry
- Add performance tracing for API routes
- Configure source maps upload
- Add Sentry badges to README
Areas to Consider
- Sample rates for error collection
- Custom tags and context
- Release tracking
Contributor guide
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 locating the Next.js application entry points, API routes, build configuration, and README referenced by the deliverables. Confirm how environment variables and source maps are handled, then define the error boundary, tracing, tags, sample rates, and release behavior. Done means production monitoring is configured, the README has badges, and the setup works with the required environment variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- backend-api-design, build-system, documentation, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100