Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Next.js wizard: metrics not shown after setup

Open
#597 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
next.js, typescript

Research direction

Start at the sentry init entry point and trace the experimental wizard's Next.js detection and feature-selection setup. Compare the generated instrumentation with the documented manual setup; done means a clean Next.js setup surfaces metrics in the Sentry project.

Written by the indexing model from the issue text.

Description

Summary

When running sentry init (the AI-powered wizard, marked EXPERIMENTAL) in a Next.js project, metrics are not displayed after the setup flow completes. The feature selection screen is presented but the resulting instrumentation does not surface metrics in the Sentry UI.

Reproduction

  1. Run sentry init in a Next.js project on a clean branch.
  2. Confirm the EXPERIMENTAL prompt to proceed.
  3. Select the desired features (e.g. Error Monitoring) via the wizard.
  4. Allow the wizard to detect platform/framework and configure Sentry.
  5. Navigate to the Sentry project — metrics are absent.

Expected behavior

Metrics should be visible in the Sentry project after wizard-assisted setup, consistent with manual setup via https://docs.sentry.io/platforms/.

Versions affected

  • CLI wizard (EXPERIMENTAL AI-powered setup)
  • Next.js (framework)
  • Org: bete-dev

Action taken on behalf of Miguel Betegón.

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
22h 3m
Merged PRs (30d)
94

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.