Two ways to the two Reacts

Next.js App Router vs TanStack Start ways of full-stack React

Two ways to the two Reacts
7 minutes by Bobae Kang

Next.js App Router and TanStack Start represent two distinct ways to the full-stack React. Both approaches have their merits, providing the React ecosystem with valuable options for implementing full-stack applications.

Meticulous AI is a tool which automatically creates and maintains a continuously evolving e2e UI test suite that covers every corner of your application – with no developer intervention required whatsoever. Backed by CTO of GitHub, Guillermo Rauch (next.js author), yc and others, it's built from the Chromium level up with a deterministic scheduling engine – making it the only testing tool that eliminates flakes.

Build a Public holidays app
20 minutes by Corina Udrescu

Build a React application that shows the national holidays for the current year, for a given country. You can retrieve a list of available countries and their holidays from the OpenHolidays API.

React Query API Design
15 minutes by T. K. Dodo

This is a comprehensive presentation transcript about React Query API design and open source maintenance lessons. Key points include: the importance of balanced API design (simple yet powerful), challenges with major version releases in open source, the value of TypeScript in initial API design, careful feature addition, and the significance of user feedback during beta testing.

When using React Server Actions with forms, the default behavior is to reset the form after submission, regardless of success or failure. To improve user experience, you can prevent form reset after failed submissions by returning the form data from the server action and using it to set default values in the form inputs. This allows users to correct and resubmit forms without re-entering all their data, while successful submissions still trigger a form reset.

Container queries, a long-awaited CSS feature now supported in all major browsers, allow developers to apply conditional CSS based on an element's container size rather than viewport dimensions. Despite being available for almost two years, adoption has been slow due to complexity and some constraints - particularly the requirement to explicitly define containers using container-type property and understanding the "golden rule" that you can't change what you measure.

how did you like this issue?

Login or Subscribe to participate in polls.

newsletters

Would you like to become a sponsor and advertise in one of the issues? Check out our media kit and get in touch.