Framework picker has no exit. Ctrl+C is the only way out and it's never mentioned
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 197
- Forks
- 51
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 94
Description
Situation:
Ran the wizard for the first time this week, setting up PostHog on my portfolio site. Once you're in the framework picker there's no way to back out : no cancel, no quit, no back.
Solutions:
Ctrl+C works, but nothing tells you that, and a first-time user shouldn't have to already know terminal conventions to escape an onboarding tool. Especially if you're already walking through what is a detailed and put together layout.
Concern/Effect:
This is the first thing a lot of people will ever run from PostHog, so the picker "trapping" you is a rough first impression.
Screenshot of the picker state below.
Suggested fix: add an exit hint to the picker prompt itself — something like "press q to quit" — and/or an explicit "None of these / exit" option at the bottom of the list. It's a low effort change, and it means nobody's first PostHog experience is being stuck.
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 running the wizard and entering the framework picker to observe its current prompt and options. Update the picker prompt or list so users can discover a quit or exit path, then verify that a first-time user can leave without relying on undocumented Ctrl+C.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100