Skip to content

[v2] Standardize the example projects #2305

Open
Task
Open
[v2] Standardize the example projects#2305
Task
Labels
scope: coreThis issue affects the core package, meaning any adapter is also affected by it.type: choreMaintenance work that doesn’t add features or fix bugs.type: docsThis issue is related to documentation, or lack thereof.v2This issue affects v2 as well.

Description

@LeCarbonator
LeCarbonator
opened on Aug 9, 2026

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 head configuration across examples.
  • Use the same port where reasonably possible.
  • Include TanStackDevtools in every example with hideUntilHover: false.
  • Apply a consistent StrictMode policy across all examples.
  • Review lingering emblem SVG files and consider replacing them with a shared TanStack logo SVG.

Activity

  1. LeCarbonator
    added
    type: docsThis issue is related to documentation, or lack thereof.
    v2This issue affects v2 as well.
    scope: coreThis issue affects the core package, meaning any adapter is also affected by it.
    type: choreMaintenance work that doesn’t add features or fix bugs.
    on Aug 9, 2026
  2. LeCarbonator
    added the
    Task
    issue type on Aug 10, 2026

  3. dasjideepak commented on Sep 25, 2026

    @dasjideepak
    dasjideepak
    on Sep 25, 2026

    Hi @LeCarbonator, I'd like to pick this up if nobody else is on it.

    I'm planning to split it into a few small PRs so they're easy to review, starting with removing the leftover TanStack Template wording and fixing duplicate or wrong package names. Then the port/head config, and after that devtools + StrictMode.

    Let me know if you'd like a different order or if anything on the list has changed.

  4. LeCarbonator commented on Sep 25, 2026

    @LeCarbonator
    LeCarbonator
    on Sep 25, 2026
    ContributorAuthor

    The order doesn't really matter. Request a review from me once the PRs are ready! Thanks for tackling it! @dasjideepak

  5. dasjideepak commented on Sep 25, 2026

    @dasjideepak
    dasjideepak
    on Sep 25, 2026

    Two quick questions before the next PRs @LeCarbonator :

    1. Ports: Angular, Lit, Preact, Solid and Svelte already use a range per framework (e.g. Svelte 3101–3109, Solid 3201–3209), while React and Vue mostly share 3001/3005. Should I move React and Vue onto the same scheme, or do you want every example on one port?
    2. StrictMode: 6 React examples use it and the rest don't. Should they all use it, or none?

  6. LeCarbonator commented on Sep 26, 2026

    @LeCarbonator
    LeCarbonator
    on Sep 26, 2026
    ContributorAuthor
    1. The ports aren't that important. I initially wrote it down since it could be confusing to have different ports per example, but since some examples work with different things that have separate defaults, I'd say just leave that part.
    2. StrictMode should be present on all of them.

    @dasjideepak

  7. dasjideepak commented on Sep 26, 2026

    @dasjideepak
    dasjideepak
    on Sep 26, 2026

    Thanks, I'll leave the ports as they are. StrictMode is now part of #2406.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    scope: coreThis issue affects the core package, meaning any adapter is also affected by it.type: choreMaintenance work that doesn’t add features or fix bugs.type: docsThis issue is related to documentation, or lack thereof.v2This issue affects v2 as well.

    Type

    Task

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions