[Feature Meta] Consolidated enhancement backlog
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- cli
Research direction
This issue is a parent tracker for enhancement planning rather than an implementation task, and it does not name files, tests, or entry points. Review the linked child issues and Discussions for a focused assignment; completion means implementing one specific child issue or updating its status here.
Written by the indexing model from the issue text.
Description
Summary
Parent tracker for consolidated enhancement planning, ordered by ease of development/workflow so execution can run top-down with minimal dependency churn.
Recommended Execution Order
- Warn when target directory already exists and is not empty (from issue 198)
- Make initialize git optional (from issue 147)
- Remove the count demo for Start (from issue 137)
- Starters documentation (from issue 102)
- Custom add-on documentation (from issue 99)
- Prompt to remove demo pages (from issue 136)
- Fix up the examples (from issue 138)
- Use add-on variables to seed
.env(from issue 135) - Custom add-on protected files (from issue 100) - deferred for now
- Add versioning to add-on metadata (from issue 139)
- Add
oxlintas option (from issue 166) - deferred for now - Add option for Zephyr (from issue 160) - deferred for now
- Pipeclean add-on creation process (from issue 132)
- Upgrade existing add-ons (from issue 129)
- Add-on upgrade strategy (from issue 131)
- Remote package management for add-ons (from issue 130)
- Documentation site (from issue 134)
- Anonymous telemetry (from issue 133)
Notes
- New design conversation should happen in Discussions.
- This issue tracks planning and sequencing; implementation can happen in focused child issues/PRs.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 185
- Avg merge
- 18h 45m
- Merged PRs (30d)
- 2
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.
More from TanStack/cli
-
create: scaffold's unlayered body styles defeat its own @layer base rules (and any shadcn theme) Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/inspector#2458 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·