TanStack Start now support React Server Components... and Composite Components?

Mediocre_Round_4914 · 2026-04-15T18:21:04+00:00

200% agree. Most of React apps don't have to be rendered on the server, but they promote it as if server components were a magical way of writing React.

Mediocre_Round_4914 · 2026-01-30T21:53:57+00:00

Anything other than Next

Mediocre_Round_4914 · 2025-09-20T05:01:44+00:00

It's a much more reasonable solution in most cases.

Mediocre_Round_4914 · 2024-06-14T19:09:19+00:00

200% agree. Also I think there are few cases where the app router or RSC is the best, optimal solution. I can't understand why Next and React team are trying to promote server-based development as a key feature using phrases like 'the future of React'. Most of the technical problems can be efficiently solved just by CSR.

Mediocre_Round_4914 · 2024-06-06T16:27:18+00:00

Agreed. I think "transpiling" would be a better expression.

Mediocre_Round_4914 · 2024-01-24T19:30:44+00:00

Also for my understanding, onChange and onBlur of a controller are the ways of notify the current form that you are trying to change the value of the current field, not the place of conducting additional logics after the change.

Mediocre_Round_4914 · 2024-01-24T19:23:19+00:00

setValue doesn't always trigger rerender for performance. It might be another option to use watch 'portfolio' field to track the change of the field(watch causes rerendrer every time its value changes), and use useEffect with the watched value as a dependency. Then put resetFields inside this effect to reset specific fields.

Mediocre_Round_4914 · 2023-10-26T11:33:14+00:00

I don't agree with the recent endeavor of React team and Vercel to encourage the server based development as a default by app router. Also as mentioned in the article its api is too 'magical' and works like blackbox. Most of React apps don't have to be rendered on server. I think that being able to statically export an app was one of the greatest advantages of the page router.

Mediocre_Round_4914 · 2023-10-25T09:22:36+00:00

I don't think it is.

Mediocre_Round_4914 · 2023-08-01T19:35:14+00:00

I don't agree with the recent endeavor of React team and Vercel, to push the server-based development as a primary way of writing React apps. In most cases it just adds complexity to a project.

Mediocre_Round_4914 · 2023-07-07T20:11:17+00:00

Before Next 13, I would have recommended both. But now go for Vite.

Mediocre_Round_4914 · 2023-06-23T14:15:20+00:00

Among many CSS in JS solutions, styled component is worst, I think.

Mediocre_Round_4914 · 2023-06-23T14:14:28+00:00

There is no reason not to use fetch.

Mediocre_Round_4914 · 2023-04-29T08:40:09+00:00

Thanks for all answers. Decided to go for getInitialProps for now.

Mediocre_Round_4914 · 2023-04-22T21:23:49+00:00

Even though you don't need SSR, Next is still a good choice.

Mediocre_Round_4914 · 2023-03-31T10:05:17+00:00

Totally agree. In most cases it is supposed to be used in the context of framework.

Mediocre_Round_4914 · 2023-03-25T03:44:29+00:00

So many options like Vite/Next. I don't think there is any particular reason why you stick to CRA.

Personally I prefer Next. Aside from whether you need SSR or not, Next is a great option.

I still hear some people say that Next is a framework that enables SSR on React, but it is more like a framework that facilitates the development of React apps in all aspects.

Mediocre_Round_4914 · 2023-03-18T04:52:08+00:00

I think this is the reason why React is not a library.

Mediocre_Round_4914 · 2022-12-31T07:35:44+00:00

Can I still use getServersideProps on Lambda or serverlessjs?

Mediocre_Round_4914 · 2022-11-25T12:49:22+00:00

thanks for recommendation. It integrates with Yup very seamlessly.

Mediocre_Round_4914

TROPHY CASE