The Quick and Dirty on React Server Components

I love React…and I am sure I am not the only one. According to many online developer surveys, React remains on top for Javascript frameworks and libraries.

React is loved by developers for its ease of scaling up UIs. Client side rendered UIs are the bread and butter of React. Its is clean and simple in design and has none of the extra unneeded bells and whistles that can get in the way.

So how does Facebook take React to the next level and make it even better?

React Server Components!!!!

Yes….the React Dev Team announced last week it wants to take our beloved client side library to the dark side….errrr…..server side ;)

What are these Server Components for?

The best practical use case would be for data and component fetching. Server components will have access to backend data and communicate between the back and the front.

Another problem that is fixed by server components is the bulk that client size components can amass. The React team is touting “Zero Bundle Size Components”. We all have experienced the slow increment of the npm packages and code snippets that can creep into our projects. This cuts down on all the extra bits of code that has to be shipped upfront that can weigh down the user experience.

It is of note that as of this writing that, React Server Components are still in the research and development phase.

I, personally cannot wait to see the outcome of this. It seems to have a ton of useful possibilities. I am ready to embrace a full robust React ecosystem.