René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature] TDK CLI integration: run a TanStack app as a local TDK resource","articleBody":"### Which project does this relate to?\n\nCreate Tanstack App\n\n### Describe the feature\n\n## 1. TanStack/cli issue\n\n**Project:** Create Tanstack App\n\n**Labels:** enhancement\n\n### Describe the feature\n\nAdd a documented, optional way to use a TanStack CLI app inside a [TDK CLI](https://github.com/tdk-landscape/tdk-cli-core) landscape, and a small add-on that makes that handoff explicit.\n\nTDK CLI (Tilt Development Kit, `@tdk-landscape/tdk-cli-core`) is a local multi-service runner. It is not a deploy and not a Compose file. Each service has a `service.json`. `tdk up \u003cstack>` starts that slice with Docker + Tilt, health-checked boot order, and `*.localhost` routing. Frontends today are Vite SPAs (`react` default, `vue` optional). TDK owns the generated Vite config (`.autogenerated/vite.config.frontend.autogenerated.ts`) and does not want a root `vite.config.ts` from the framework provider.\n\nTanStack CLI and TDK CLI solve different problems:\n\n| Tool | Owns |\n| --- | --- |\n| `tanstack create` / `tanstack add` | App scaffold: Router or Start, add-ons, deployment |\n| `tdk project` / `tdk resource` / `tdk up` | Local landscape: ports, stacks, Docker, Tilt, proxy |\n\nThere is no shared contract today. A TanStack app dropped into a TDK repo does not get a `service.json`, and `tdk resource --type frontend` cannot scaffold TanStack Router or Start.\n\nRequested outcome: one recipe that works from either CLI, with Router-only as the first supported path and Start as an explicit second path.\n\n#### Proposed use\n\nFrom an existing TDK project:\n\n```bash\ntdk project --yes\ntdk resource shop-web --type frontend --framework tanstack-router --stack shop --yes\ntdk resource orders-api --type backend --stack shop --yes\ntdk up shop\n```\n\nFrom TanStack CLI, opt in with an add-on instead of a new required flag:\n\n```bash\ntanstack create shop-web --router-only --add-ons tdk -y\n# later, inside a TDK project:\ntdk up shop\n```\n\nStart stays available, but not by pretending it is the current Vite SPA provider:\n\n```bash\n# phase 2 — Start dev server is brought in, TDK does not rewrite vite.config.ts\ntanstack create shop-web --blank --add-ons tdk -y\ntdk resource shop-web --type bring-your-own --stack shop\n```\n\n#### What the TanStack add-on should write\n\nCategory `tooling`. No runtime dependency on TDK inside the generated app.\n\n- `service.json` with `type: \"frontend\"`, `framework`, `stack`, and the port convention TDK already uses (frontends in 3000–3999).\n- A short `TDK.md` (or a section in the generated README) with install, `tdk up`, and the boundary: TDK is local only; deploy stays on the TanStack deployment add-on (Cloudflare, Netlify, and so on).\n- `package.json` script hints only, for example `\"dev:tdk\": \"tdk up\"` when the CLI is present. Do not fail `pnpm dev` if TDK is not installed.\n- Nothing that overwrites TanStack Start’s `vite.config.ts` in v1.\n\nRouter-only maps cleanly onto TDK’s provider contract (Vite SPA, no root `vite.config.ts`, starter `index.html` + entry). Start does not: Start owns Vite config and is SSR. Shipping Start as a normal `--framework` provider would fight both generators. Call that out in the issue so it is not implemented as a drive-by.\n\n#### Acceptance\n\n- Docs page: “Use with TDK CLI”, linked from TanStack CLI docs and from the add-on details (`tanstack create --addon-details tdk`).\n- `--router-only --add-ons tdk` produces a `service.json` that `tdk config verify` accepts once the TDK provider exists.\n- `--blank` / Start + `tdk` documents the bring-your-own path and does not emit a provider framework id TDK will reject.\n- Add-on is optional. Default `tanstack create` is unchanged.\n- JSON introspection includes the add-on (`--list-add-ons --json`).\n\n### Additional context\n\nTDK frontend provider contract: https://github.com/tdk-landscape/tdk-cli-core/blob/main/docs/frontend-framework-providers.md\n\nRelevant TDK commands:\n\n```bash\ntdk resource my-app --type frontend --stack api\ntdk resource my-vue-app --type frontend --framework vue --stack api\n```\n\n`framework` is an enum on `service.json` (`react`, `vue` today). Unknown ids are rejected before files are written. A TanStack provider has to be registered in TDK (`cli/src/frontend-frameworks/`, Starlark Vite templates, `service-schema.json`). That half belongs in `tdk-landscape/tdk-cli-core`; companion issue linked below.\n\nCompanion issue (file against TDK, link here): feat(frontend) tanstack-router provider, and a TanStack Start bring-your-own path.\n\nNon-goals:\n\n- Replacing TanStack deployment add-ons with TDK. TDK does not deploy.\n- Making TDK a required toolchain.\n- Teaching TDK’s React/Ink CLI UI about TanStack. This is about generated apps and `service.json`, not the TDK terminal UI.\n\n\n### Additional context\n\nlinked issue https://github.com/tdk-landscape/tdk-cli-core/issues/234","author":{"url":"https://github.com/odykyi","@type":"Person","name":"odykyi"},"datePublished":"2026-10-01T21:28:31Z","url":"https://github.com/TanStack/cli/issues/520"}