Next.js Best Practices: Protecting Server Code From Client Access Code Ryan podcast

Artwork

Tech Ryan Solomon

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://ppacc.player.fm/legal.

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

1+ y ago 15:06

Share

MP3•Episode home

Fetch error

Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on July 24, 2025 17:04 (1M ago)

What now? This series will be checked again in the next hour. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.

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://ppacc.player.fm/legal.

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.

… continue reading

297 episodes

#Tech #Ryan Solomon

Artwork

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

published 1+ y ago

Share

MP3•Episode home

Fetch error

Hmmm there seems to be a problem fetching this series right now. Last successful fetch was on July 24, 2025 17:04 (1M ago)

What now? This series will be checked again in the next hour. If you believe it should be working, please verify the publisher's feed link below is valid and includes actual episode links. You can contact support to request the feed be immediately fetched.

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://ppacc.player.fm/legal.

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.

… continue reading

297 episodes

#Tech #Ryan Solomon

All episodes

×

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

Listen to 500+ topics

Listen to this show while you explore