Option to keep setup to keys and config, or confirm the file list before editing app code

Open
#1,463 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

The request is a design change to how the wizard writes code: a setup-only mode or a confirmation step before editing files. Start by finding where the wizard collects its planned file changes and dependency installs before writing them. Done would need a design agreed in the thread (see #113 for monorepo handling) before any code is written.

Written by the indexing model from the issue text.

Description

What happened: In a monorepo that already has one in-house package owning every PostHog SDK import (enforced by lint and dependency rules), the wizard:

  • added @posthog/ai, ai and 7 OpenTelemetry packages straight to the app
  • imported them outside that package
  • changed 38 files (+953 / −132) across the app and four workspace packages

We stashed all of it and kept only the project token.

Suggestion: one or both of:

  • a "setup only" mode: project, keys, env vars and a check that events arrive, without editing application code
  • a confirmation step listing the files and dependencies it's about to change, before it writes them

Related: #113 (monorepo support).

The onboarding itself (project, dashboard, notebook report) was smooth. This is what stopped us from keeping the code changes.

Dominant language
TypeScript
Stars
204
Forks
54
Avg merge
1d 5h
Merged PRs (30d)
51

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 PostHog/wizard

All issues in PostHog/wizard

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.