[v2] Standardize the example projects
Open
Nobody has claimed this yet.
scope: core
type: chore
type: docs
v2
- Dominant language
- TypeScript
- Stars
- 6.7k
- Forks
- 682
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 7
Description
As a final cleanup pass, the example projects should be reviewed for consistent naming, configuration, tooling, and branding. Some examples originated from TanStack Template and still contain differences or leftover assets that should be addressed.
Checklist
- Remove any remaining TanStack Template wording.
- Review package names for duplicates or incorrect names.
- Standardize the
headconfiguration across examples. - Use the same port where reasonably possible.
- Include
TanStackDevtoolsin every example withhideUntilHover: false. - Apply a consistent
StrictModepolicy across all examples. - Review lingering
emblemSVG files and consider replacing them with a shared TanStack logo SVG.
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.
Research direction
Start by inventorying the example projects and comparing their package names, head configuration, ports, TanStackDevtools setup, StrictMode usage, and remaining emblem assets. Review the checklist across every example; the work is done when the examples follow the requested naming, configuration, tooling, and branding conventions without TanStack Template leftovers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100