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

Init success output doesn't prove setup worked

Open
#1,381 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

No file or test is named. Start by locating the CLI code that renders the static sentry init summary and review related issue #1379. Done should make the created project and configured features unmistakable and provide a clear signal about whether data was sent successfully.

Written by the indexing model from the issue text.

Description

After sentry init completes, the terminal shows a static install summary (SDK package commands, project settings URL, docs link, enabled features). That leaves users unsure which project was created and whether anything actually reached Sentry.

Observed end state on Next.js App Router (@sentry/nextjs):

  • "Sentry SDK installed successfully"
  • platform, directory, and install commands
  • Project URL pointing at project settings (e.g. …/settings/projects/<slug>/)
  • Docs URL
  • Features listed as set up (Error Monitoring, Session Replay, Tracing, Logging)

Gaps reported after that screen:

  • Project outcome is easy to miss or hard to trust from the settings URL alone
  • No test/sample error
  • No CLI follow-through showing events or logs arriving
  • No signal that data was sent successfully

Related: #1379 (finish with a clear summary of what was configured)

Reported by Dhrumil Parekh.

Requested by Dhrumil Parekh.

--

View Junior Session [Sentry]

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
23h 54m
Merged PRs (30d)
103

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.