Nextjs for frontend option, tailwind for UI

[MetythornPenn]

Privileged issue

• [X] I'm @tiangolo or he asked me directly to create an issue here.

Issue Content

Since Nextjs has dominate the frontend world, i want to have option to select frontend in NextjS or React with vits. for the UI also i want to have tailwind option. Thank you

[joshwisehub]

Nextjs has not dominated its all about hype.Most companies still use plain react .Nothing beats type safety routing Tanstack router really works well and you can still use RSC with plain react and when react compiler becomes stable mots react problems will be solved.Remember Nextjs is backed by Vercel so watch out their Marketing Strategies,Also to add if you start to add react meta framewroks also remix people will come and say the same. On the other hand Taiwlind CSS is fine.Tailwind has dominated the industry.

[myanalysis]

I vote for Svelte! And Tailwinds.

[damascene]

+1 for Svelte

[GitTom]

Tailwind (definitely) and shadcn/ui (arguably) have become the most popular options for UI.

I understand that others want to point out that they think there are better options, and that is true, but for popularity I don't think it is even close.

People want to fight against Next.js, React etc. because they are so dominant, and I applaud that instinct, but if we want this template to be much more popular then I think a Next.js / Tailwind / shadcn variant would really help.

[developerdev2007]

I will vote for Nextjs for his server side rendring and performance 👍,Tailwind css and shadcn ui will be best . And if you like to implement it , I will always with you 😊

[yunge]

This repo is for Python developers, Next.js is too complex(debug/deploy) for Python devs.

At the very start, Next.js is more convenient to use than React, but once you encounter problems, you might get stuck.

For this repo, the front-end framework should be the framework that Python devs are most like to use. Web developers can directly opt for a full-stack development approach using Next.js + Drizzle/Prisma.

[jonbzt]

I'm not sure this is really a valid request/issue in the context of this repo. As mentioned by @yunge This is a repo oriented for python devs but more than that, it is supposed to be an opinionated template. All the frameworks and libraries used in this repo are examples to show how a full-stack application using FastAPI as a backend would look like.

If it match your needs great use it as is. Otherwise you can do the modifications by yourself or create a fork for example to support NextJS. Which I'm sure a lot of devs would appreciate 😉

On the other hand using NextJS with an app that already has a backend running is kind of killing the point of NextJS since it's Full-stack oriented meta-framework. The latest versions of Next (as of Next 14) clearly show the vision of Vercel to handle the whole tech stack and not only allow to plug-and play SPA apps into existing backends.

[Raiwulf]

How is this an issue? You are ordering an ice cream in a steak house.

[wesenbergg]

I wonder if people have interest in fork with Svelte + Tailwindcss (+shadcn)? 🤔

[arab0v]

Voting to delete the frontend part from the project

[whinc]

TANSTACK START is a good alternative to nextjs.

[cubxxw]

Is there a corresponding implementation of the next front-end?

[ChrisSQL]

NextJS all the way. As soon as i swapped over SEO was a hundred times better.

[Michael-Forson]

Waiting for Next js starter template

[athrael-soju]

Incoming...

• [x] Next.js 15
• [x] Tailwind css v4
• [x] Shadcn
• [x] Framer Motion

#1733

[nemanjam]

I took the two existing PRs one step further and made a fork for anyone that would like to use Next.js option for frontend:

• https://github.com/fastapi/full-stack-fastapi-template/pull/1733
• https://github.com/fastapi/full-stack-fastapi-template/pull/1606

I cleaned up components, made them reusable, rendered pages on server, server actions for forms, HttpOnly cookie auth, Github login, ShadcnUI and Tailwind 4, Next.js 16, monorepo, runtime environment variables for a reusable Docker image.

Here is the link from the repository: https://github.com/nemanjam/full-stack-fastapi-template-nextjs

[tiangolo]

The full-stack-fastapi-template was just migrated to shadcn/ui and Tailwind. 🎉

The routing is done with TanStack router (and querying with TanStack query), not Next.js.

As this project is mainly about handling data under a login page more than a static content site, there's not much benefit from going with Next.js, and there are benefits from the more comprehensive types in TanStack router.

I'll now close this one. ☕

If any of you has any other ideas, it's best to start them in a GitHub Discussion.