Next.js Best Practices: Protecting Server Code from Client Access

Code Ryan

Content provided by Ryan Solomon. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Ryan Solomon or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

2y ago 15:06

MP3•Episode home

Archived series ("Inactive feed" status)

When? This feed was archived on October 04, 2025 09:08 (2M ago). Last successful fetch was on July 24, 2025 17:04 (5M ago)

Why? Inactive feed status. Our servers were unable to retrieve a valid podcast feed for a sustained period.

What now? You might be able to find a more up-to-date version using the search function. This series will no longer be checked for updates. If you believe this to be in error, please check if the publisher's feed link below is valid and contact support to request the feed be restored or if you have any other concerns about this.

GitHub: https://github.com/coderyansolomon/server-only

API: https://developer.themoviedb.org/reference/intro/getting-started

In this insightful Next.js tutorial, viewers will learn the crucial technique of keeping server-only code out of the client environment. The tutorial delves into the common issue faced in JavaScript modules shared between server and client components, where server-specific elements, such as private API keys, may unintentionally become exposed on the client side. By focusing on a practical example of a data-fetching function, the tutorial demonstrates how seemingly universal functions can inadvertently include server-only code.

297 episodes

#Tech #Ryan Solomon