News for hackers. Stuff that matters.

A comment on Denial of service and source code exposure in React Server Components. Parent comment

Re:Denial of service and source code exposure in React Serve... by berekuk on Thursday December 11, 2025 @10:53PM (#46240719)
If I control both the backend and the frontend, yes. Server-only async components on top of layout/page component hierarchy, components -> DTO layer -> Prisma. Similar to this: https://nextjs.org/blog/security-nextjs-server-components-ac...

You still need API routes for stuff like data-heavy async dropdowns, or anything else that's hard to express as a pure URL -> HTML, but it cuts down the number of routes you need by 90% or more.

[ Parent | on HN ]
Re:Denial of service and source code exposure in React Serve... by skydhash on Friday December 12, 2025 @05:32AM (#46242761)
You’re just shifting the problem from HTTP to an adhoc protocol on top of it.
[ Parent | on HN ]
Re:Denial of service and source code exposure in React Serve... by afavour on Friday December 12, 2025 @09:54AM (#46244707)
Yes but they’re also shifting the problem from one they explicitly have to deal with themselves to one the framework handles for them.

Personally I don’t like it but I do understand the appeal.

[ Parent | on HN ]
Re:Denial of service and source code exposure in React Serve... by skydhash on Friday December 12, 2025 @09:57AM (#46244733)
Maybe, but you go from one of the most tested protocol with a lot of tooling to another with not even a specification.
[ Parent | on HN ]