Загрузка видео...

Не удалось загрузить видео

На главную

Next.js security tip: Use "server only" for the code that should never be exposed to the client.

109,311 просмотров • 1 год назад •via X (Twitter)

Комментарии: 10

Фото профиля Andric
Andric1 год назад

Never understood why server only is a package and not a directive.

Фото профиля Matija Marohnić 🦋
Matija Marohnić 🦋1 год назад

This is really good, it's surprising that among all of talk about security concerns about RSCs and Server Actions in Next.js I've never heard about this.

Фото профиля Alex Sidorenko
Alex Sidorenko1 год назад

Here is a great in-depth article about security in Next.js

Фото профиля Vance Lucas
Vance Lucas1 год назад

The fact that it is even possible to accidentally ship sensitive server code to the client is a huge red flag. 🚩🚩🚩

Фото профиля Windfan
Windfan1 год назад

it's very easy to get confused by "use server" and `import "server-only"`. Now I have 3 different function files to help me, post.server.ts(using server-only), post.action.ts(using "use server") and post.ts(the functions that can be called by server or client components)

Фото профиля Phong
Phong1 год назад

in a few years I swear we are going to go full circle again back to client server separation as the latest fad

Фото профиля Terry Carson
Terry Carson1 год назад

Nice one...thanks

Фото профиля Prasenjit
Prasenjit1 год назад

That's a crucial tip! Keeping sensitive code on the server side is essential for protecting your application. It helps ensure that no confidential data is exposed to users. Thanks for sharing this important reminder!

Фото профиля Artur
Artur1 год назад

We need "use security" directive ASAP😁

Фото профиля fulco
fulco1 год назад

Wish this was a directory like with sveltekit

Похожие видео