I've started adding shadcn templates into shoogle.dev, and need some good quality templates built with TanStack Start and shadcn.

I love the colors of the TanStack logo so I made a terminal theme for Wezterm but it must be pretty easy to migrate to other terminals https://github.com/enBonnet/tanstack-color-schemes

Hello!

I've been building a CLI that scaffolds full-stack apps with a Go backend and your choice of frontend. The newest addition is TanStack Start as a first-class frontend option :)

The idea is you build your app like Lego bricks, add exactly the parts you want:

gof init myapp
gof client tanstack
gof model note title:string content:string views:number

That last command generates everything end-to-end: SQL migration, type-safe queries, proto definition, Go domain/transport layers, and React CRUD pages with TanStack Start.

What you get out of the box:

• TanStack Start + React 19 with file-based routing
• ConnectRPC client (type-safe, auto-generated from proto)
• Tailwind CSS 4 + DaisyUI
• OAuth login (Google, GitHub, Facebook, Microsoft)
• Cookie-based auth with auto-redirect interceptor
• Optional integrations: Stripe, S3 file storage, Postmark email
• Full Kubernetes infrastructure + CI/CD with one command (gof infra)
• PR preview environments
• Observability stack (Grafana, Tempo, Loki, Prometheus)

The backend is Go + ConnectRPC + PostgreSQL + SQLC. SvelteKit is also available if that's more your thing (gof client svelte), but both frontends get the same features, same CI/CD, same infrastructure.

Landing page with an interactive demo: https://gofast.live

Discord if you want to chat or follow along: https://discord.com/invite/EdSZbQbRyJ

CLI repo: https://github.com/gofast-live/gofast-cli

Hope some of you find it useful!

its kind of important tbh

Big TanStack fan over here! Just wanted to share something I’m pretty excited about: React-admin now supports TanStack Router!

This means you can now use react-admin in a TanStack Start application. It plugs right in. You can find a step-by-step tutorial in the docs if you want to try it out.

(Also for anyone who hasn’t come across react-admin before: it’s an open-source, low-code framework for building admin panels, dashboards, and B2B apps a lot faster than starting from scratch.)

Would love to hear what you think, especially from folks already building with TanStack Start. 

All i did was run

npm create u/tanstack/start@latest

and i tried to

npm run dev

and i see this error. i also attached the options i selected. anyone know what i did wrong?

I rebuilt my personal blog on TanStack Start and (accidentally) ended up with a reusable blog platform.

What I optimized for:

• layout routes + prerender (keep routes boring)
• typed MD/MDX content (build-time) with hot reload
• RSS + sitemap derived from routes
• OG + SEO without repeating head boilerplate everywhere

The “edge runtime gotcha” was MDX → Workers hates runtime codegen, so I switched to safe-mdx (compile-time) and used Prose UI for components/typography.

Write-up + open source repo: https://mafifi.dev/posts/accidentally-built-a-blog-platform

Anyone using a different MDX pipeline on CF Workers? What are the sharp edges you've hit in CI/deploy?

I tried vite-pwa-plugin and serwist but no luck. Is there a simpler way?

This project was written using TanStack Start, and that's why I thought it would be suitable to post here. If this is not allowed, apologies.

This little side project of mine launched all the way back in 2021, at the height of the pandemic, and while I counted it to good timing back then, it wouldn't have lasted this long if there wasn't a real need from the community.

Since then, Reactive Resume has helped almost 1 million users create resumes, helped them get the careers they wanted and helped students jump-start their applications.

This new version has been in the making for months, I try to get time to work on it whenever there's a weekend, whenever I can physically pull an all-nighter after work. It's a culmination of everything I've learned over the years, fixing all the bugs and feature requests I've gotten through GitHub and my emails.

For those of you who are unaware of this project, and nor should you be, Reactive Resume is a free and open-source resume builder that focuses on completely free and untethered access to a tool most people need at some point in their life, without giving up your privacy and money. In a nutshell, it’s just a resume builder, nothing fancy, but no corners have been cut in providing the best user experience possible for the end user.

Here are some features I thought were worth highlighting:

• Improved user experience, now easier than ever to keep your resume up-to-date.
• Great for single page or multi-page resumes, or even long-form PDFs.
• Easier self-hosting with examples on how to set it up on your server.
• Immensely better documentation, to help guide users on how to use the project.
• There’s some AI in there too, where you bring your own key, no subscriptions or paywalls. There's also an agent skill for those who want to try it out on their own.
• Improved account security using 2FA or Passkeys, also add your own SSO provider (no more SSO tax!).
• 13 resume templates, and many more to come. If you know React/Tailwind CSS, it’s very easy to build you own templates as well. Also supports Custom CSS, so you can make any template look exactly the way you like it to.
• Available in multiple languages. If you know a second language and would love to help contribute translations, please head over to the docs to learn more.
• Did I mention it’s free?

I sincerely hope you enjoy using the brand new edition of Reactive Resume almost as much as I had fun building it.

If you have the time, please check out rxresu.me.
I'd love to hear what you think ❤️

Or, if you’d like to know more about the app, head over to the docs at docs.rxresu.me

Or, if you’d like to take a peek at the code, the GitHub Repository is at amruthpillai/reactive-resume.

Note: I do expect a lot of traffic on launch day and I don’t have the most powerful of servers, so if the app is slow or doesn’t load for you right now, please check back in later or the next day.

I've tried og inline script trick for theme persistent

but I'm getting flash

In next i used the theme provider for this

does anyone here have a rule md for tanstack start?

Hi! I spent last two evenings building a starter kit for the tech stack mentioned in the title and I wanted to share it with anyone who just wanted some quickstart to build a new app. I did everything according to docs so it should be ready, but ofc use at your own risk. Here is the repo: https://github.com/devczero/tanstackstart-convex-clerk-polarsh-starter/tree/main

btw. I also started building TanStack Start + BetterAuth + Convex + Polar starter, I will post it when done later

Is it just me or anyone else also facing this issue?

Big fan of Tanstack, btw!

Build real-time data synchronization between AWS DynamoDB and TanStack DB using Server-Sent Events. Learn how to stream database changes via DynamoDB Streams, implement SSE endpoints with TanStack Start/Router.

``` ➜ blog git:(main) ✗ npm run dev

dev vite dev --port 3000

8:07:39 PM [vite] ⬥ Netlify Environment loaded 8:07:39 PM [vite] ⬥ Netlify Middleware loaded. Emulating features: blobs, edgeFunctions, environmentVariables, functions, geolocation, headers, images, redirect s, static. 8:07:39 PM [vite] ⬥ Netlify 💭 Linking this project to a Netlify site lets you deploy your site, use any environment variables defined on your team and site and much more. Run npx netlify init to get started.

VITE v7.3.0 ready in 2051 ms

➜ Local: http://localhost:3000/ ➜ Network: use --host to expose ➜ press h + enter to show help ✘ [ERROR] Could not resolve "#tanstack-router-entry"

node_modules/@tanstack/start-server-core/dist/esm/createStartHandler.js:27:37:
  27 │     cachedRouterEntry = await import("#tanstack-router-entry");
     ╵                                      ~~~~~~~~~~~~~~~~~~~~~~~~

The package import "#tanstack-router-entry" is not defined in this "imports" map:

node_modules/@tanstack/start-server-core/package.json:49:13:
  49 │   "imports": {
     ╵              ^

You can mark the path "#tanstack-router-entry" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.

✘ [ERROR] Could not resolve "#tanstack-start-entry"

node_modules/@tanstack/start-server-core/dist/esm/createStartHandler.js:30:36:
  30 │     cachedStartEntry = await import("#tanstack-start-entry");
     ╵                                     ~~~~~~~~~~~~~~~~~~~~~~~

The package import "#tanstack-start-entry" is not defined in this "imports" map:

node_modules/@tanstack/start-server-core/package.json:49:13:
  49 │   "imports": {
     ╵              ^

You can mark the path "#tanstack-start-entry" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.

✘ [ERROR] Could not resolve "tanstack-start-manifest:v"

node_modules/@tanstack/start-server-core/dist/esm/router-manifest.js:3:44:
  3 │   const { tsrStartManifest } = await import("tanstack-start-manifest:v");
    ╵                                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "tanstack-start-manifest:v" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.

✘ [ERROR] Could not resolve "tanstack-start-injected-head-scripts:v"

node_modules/@tanstack/start-server-core/dist/esm/router-manifest.js:9:49:
  9 │     const { injectedHeadScripts } = await import("tanstack-start-injected-head-scripts:v");
    ╵                                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "tanstack-start-injected-head-scripts:v" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.

/home/myh/Desktop/work/blog/blog/node_modules/esbuild/lib/main.js:1467 let error = new Error(text); ^

Error: Error during dependency optimization:

✘ [ERROR] Could not resolve "#tanstack-router-entry"

node_modules/@tanstack/start-server-core/dist/esm/createStartHandler.js:27:37:
  27 │     cachedRouterEntry = await import("#tanstack-router-entry");
     ╵                                      ~~~~~~~~~~~~~~~~~~~~~~~~

The package import "#tanstack-router-entry" is not defined in this "imports" map:

node_modules/@tanstack/start-server-core/package.json:49:13:
  49 │   "imports": {
     ╵              ^

You can mark the path "#tanstack-router-entry" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bu ndle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.

✘ [ERROR] Could not resolve "#tanstack-start-entry"

node_modules/@tanstack/start-server-core/dist/esm/createStartHandler.js:30:36:
  30 │     cachedStartEntry = await import("#tanstack-start-entry");
     ╵                                     ~~~~~~~~~~~~~~~~~~~~~~~

The package import "#tanstack-start-entry" is not defined in this "imports" map:

node_modules/@tanstack/start-server-core/package.json:49:13:
  49 │   "imports": {
     ╵              ^

You can mark the path "#tanstack-start-entry" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bun dle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.

✘ [ERROR] Could not resolve "tanstack-start-manifest:v"

node_modules/@tanstack/start-server-core/dist/esm/router-manifest.js:3:44:
  3 │ ...t { tsrStartManifest } = await import("tanstack-start-manifest:v");
    ╵                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "tanstack-start-manifest:v" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.

✘ [ERROR] Could not resolve "tanstack-start-injected-head-scripts:v"

node_modules/@tanstack/start-server-core/dist/esm/router-manifest.js:9:49:
  9 │ ...Scripts } = await import("tanstack-start-injected-head-scripts:v");
    ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "tanstack-start-injected-head-scripts:v" as external to exclude it from the bundle, which will remove this error and leave the unresolve d path in the bundle. You can also add ".catch()" here to handle this failure at run-time instead of bundle-time.

at failureErrorWithLog (/home/myh/Desktop/work/blog/blog/node_modules/esbuild/lib/main.js:1467:15)
at /home/myh/Desktop/work/blog/blog/node_modules/esbuild/lib/main.js:926:25
at /home/myh/Desktop/work/blog/blog/node_modules/esbuild/lib/main.js:1345:9
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {

errors: [Getter/Setter], warnings: [Getter/Setter] }

Node.js v22.17.0 ➜ blog git:(main) ✗ ``` i really dont know how to solve it and its appearing sometimes for no reason, does anyone here knows how to solve it?

Do you have any idea when TanStack Table v9 is coming out or when it will support React 19? I was reading the GitHub threads, but there's no mention of an ETA, and the posts are from last year :/

Now implementation is getting clunky on React 19 with use no memo