Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

React tip: "use client" misconceptions (1/5) 🚫 You need to mark EVERY individual file with "use client" to ensure it is a Client Component. ✅ You only need to mark each client entry point ONCE. Modules imported into a "use client" file are already part of the client bundle.... (0:05) Adding "use client" to `3.js` marks the file as a client entry point, including it in the client bundle. (0:11) Importing `d()` into `3.js` (a client entry point) also includes it in the client bundle. (0:14) Adding "use client" to `4.js` has no additional bundling effect on `d()` because it is already part of the client bundle. (0:23) All modules (and their dependencies) imported to `3.js` are included in the client bundle. (0:26) Removing "use client" from `3.js` moves it and its dependencies into the server bundle.show more

Delba

99,962 subscribers

157,365 views • 2 years ago •via X (Twitter)

Science & Technology Education

Anya Rossi• Live Now

Private livecam show

10 Comments

Delba2 years ago

React docs: They recently got a facelift with some diagrams and code playgrounds. Props to the React team 🫡

chan2 years ago

these visualizations are amazing, Delba!

Delba2 years ago

Thank you!

Rotimi Best2 years ago

Please give Delba a raise, she is a must keep in the React ecosystem now. These videos are so damn important right now.

Jan Nicklas2 years ago

in 4.js, it's not specified whether it is a client component directly. so to figure it out, a dev (or tool) needs to scan all imports across the entire codebase. is that really a good thing?

Delba2 years ago

It's up to you. It's a bit like DRY, you can do it every time, but it's a bit heavy-handed to do it prematurely. I think we'll develop a feel for it.

janka2 years ago

hell yeah this is beautiful also i think blue should canonically be the color of client components! i tend to go client=blue & server=yellow but that can get a bit busy, the dimmed grey works much better here

Delba2 years ago

Blue it is. It has been decided 🤝

Steven Tey2 years ago

I felt like I was in a Next.js-themed Minecraft server while watching this video – fantastic work!

Delba2 years ago

Haha, cheers Steven! Congrats on getting engaged 🖤

Related Videos

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

Delba

43,989 views • 2 years ago

Today, Oversight Committee laid it all out for the American people. This is how the Bidens' scheme works: 1. Foreign client has a problem. 2. Client pays a Biden. 3. VP Biden travels to the country. 4. VP Biden leverages U.S. influence to force favorable outcomes for the client. 5. THE BIDEN FAMILY EARNS THEIR FEE. 💵 6. Find a new foreign client. 7. Wash. Rinse. Repeat.

Today, Oversight Committee laid it all out for the American people. This is how the Bidens' scheme works: 1. Foreign client has a problem. 2. Client pays a Biden. 3. VP Biden travels to the country. 4. VP Biden leverages U.S. influence to force favorable outcomes for the client. 5. THE BIDEN FAMILY EARNS THEIR FEE. 💵 6. Find a new foreign client. 7. Wash. Rinse. Repeat.

Congressman William Timmons

865,896 views • 3 years ago

In LiveView, we keep the state in one place - the server - and it simplifies a lot. But sometimes the state on the client is preferred, or even necessary, and we can't use LiveView for that part. Unless we have a LiveView that runs on the client 👀 Using Popcorn, we managed to run LiveView fully in the browser – here's a POC 🎉 The approach is to have a fully client-side LiveView rendered by a server-side one, and they can communicate with each other. Try it out:

In LiveView, we keep the state in one place - the server - and it simplifies a lot. But sometimes the state on the client is preferred, or even necessary, and we can't use LiveView for that part. Unless we have a LiveView that runs on the client 👀 Using Popcorn, we managed to run LiveView fully in the browser – here's a POC 🎉 The approach is to have a fully client-side LiveView rendered by a server-side one, and they can communicate with each other. Try it out:

Elixir by Software Mansion

13,537 views • 7 months ago

If you want to be able to call server functions from the client, RPC is often the move. The Bun + Better Call combo gets you a fullstack solution in very little code. Server, Client, bundling and HMR 👌 had to record a little video showing the setup

If you want to be able to call server functions from the client, RPC is often the move. The Bun + Better Call combo gets you a fullstack solution in very little code. Server, Client, bundling and HMR 👌 had to record a little video showing the setup

Wes Bos

103,642 views • 9 months ago

first step was getting llama cpp to play nice with electron js so that we can run the model I fine tuned on the client, a couple errors but eventually got it wired up with node-llama-cpp bindings. this way the model + app can be shipped to the user (client) and run offline

first step was getting llama cpp to play nice with electron js so that we can run the model I fine tuned on the client, a couple errors but eventually got it wired up with node-llama-cpp bindings. this way the model + app can be shipped to the user (client) and run offline

anton

16,499 views • 2 years ago

Katie Miller: “Does an Epstein client list exist and is the government in possession of it?” Todd Blanche: “No. ..To be honest with you, I don’t even know what a client list is. …I have not seen such a list.”

Katie Miller: “Does an Epstein client list exist and is the government in possession of it?” Todd Blanche: “No. ..To be honest with you, I don’t even know what a client list is. …I have not seen such a list.”

PatriotTakes 🇺🇸

321,312 views • 2 months ago

Financial Advisor survey on crypto: - 59% do not invest in it or plan to in the future - 26% don't invest in it now but expect to in the future - 12% use crypto based on client request - 3% use crypto on advisor recommendation

Financial Advisor survey on crypto: - 59% do not invest in it or plan to in the future - 26% don't invest in it now but expect to in the future - 12% use crypto based on client request - 3% use crypto on advisor recommendation

Bitcoin News

260,101 views • 1 year ago

If you’re playing on MonkeyTilt, the outcome might already be decided BEFORE you bet “The cryptography behind every bet has always been sound” We tested it It isn’t... we sent two different client seeds for the same nonce same result both times the server is ignoring the client seed entirely the player has ZERO influence on outcomes — what we did — opened the MonkeyTilt provably fair verifier with a revealed server seed entered nonce 1 → got 3.04x changed the client seed same server seed, same nonce → 3.04x changed it again → 3.04x the client seed has ZERO effect on the outcome — why this matters — in a provably fair system the outcome is derived from: -server seed -client seed -nonce the client seed exists so the player contributes randomness the server CAN’T predict if it’s ignored the server knows every outcome BEFORE you bet the hash commitment proves nothing because the server already controls all the inputs — not a frontend bug — we checked the network traffic the verifier sends a WebSocket request with: -client seed -server seed -nonce the server receives different client seeds and returns the same result anyway request 1 → client_seed “Clientseed123456789” → 3.04x request 2 → client_seed “NEWSEED12345” → 3.04x this is the server ignoring input not a display issue — live bet traffic — placing a Limbo bet returns: -random_multiplier -total_payout -round_closed that’s it no hash no seed reference no nonce no proof seeds are fetched from a separate endpoint game engine and seed system are DISCONNECTED — nonce verification — you can only verify nonces you’ve already played in a real system all outcomes are predetermined once the server seed is committed - they’re deterministic blocking future nonces suggests results don’t exist until you bet — summary — -client seed ignored by server -no cryptographic proof in bet responses -game engine and seed system DISCONNECTED -nonce verification restricted this isn’t provably fair it looks like provably fair UI on top of server side RNG MonkeyTilt should probably address this anyone can verify this themselves in 60 seconds - open the verifier, change the client seed, watch the result stay the same

If you’re playing on MonkeyTilt, the outcome might already be decided BEFORE you bet “The cryptography behind every bet has always been sound” We tested it It isn’t... we sent two different client seeds for the same nonce same result both times the server is ignoring the client seed entirely the player has ZERO influence on outcomes — what we did — opened the MonkeyTilt provably fair verifier with a revealed server seed entered nonce 1 → got 3.04x changed the client seed same server seed, same nonce → 3.04x changed it again → 3.04x the client seed has ZERO effect on the outcome — why this matters — in a provably fair system the outcome is derived from: -server seed -client seed -nonce the client seed exists so the player contributes randomness the server CAN’T predict if it’s ignored the server knows every outcome BEFORE you bet the hash commitment proves nothing because the server already controls all the inputs — not a frontend bug — we checked the network traffic the verifier sends a WebSocket request with: -client seed -server seed -nonce the server receives different client seeds and returns the same result anyway request 1 → client_seed “Clientseed123456789” → 3.04x request 2 → client_seed “NEWSEED12345” → 3.04x this is the server ignoring input not a display issue — live bet traffic — placing a Limbo bet returns: -random_multiplier -total_payout -round_closed that’s it no hash no seed reference no nonce no proof seeds are fetched from a separate endpoint game engine and seed system are DISCONNECTED — nonce verification — you can only verify nonces you’ve already played in a real system all outcomes are predetermined once the server seed is committed - they’re deterministic blocking future nonces suggests results don’t exist until you bet — summary — -client seed ignored by server -no cryptographic proof in bet responses -game engine and seed system DISCONNECTED -nonce verification restricted this isn’t provably fair it looks like provably fair UI on top of server side RNG MonkeyTilt should probably address this anyone can verify this themselves in 60 seconds - open the verifier, change the client seed, watch the result stay the same

CoinBets🔍

20,973 views • 4 months ago

Introducing Open MCP Client 🪁 Chat with any MCP server in your own app, just grab a URL from . The team and I vibe coded with Cursor this weekend and built: 1. The first web-based MCP client (link👇) 2. An open-source client you can add into any app How it's built It uses CopilotKit🪁 for the client and interactivity layer, and connects to a 40 line LangGraph ReAct agent that coordinates MCP calls. Hosted on Vercel. Kudos to Suhas Deshpande and Tyler Slaton for hacking and thanks to Harrison Chase for pointers!

Introducing Open MCP Client 🪁 Chat with any MCP server in your own app, just grab a URL from . The team and I vibe coded with Cursor this weekend and built: 1. The first web-based MCP client (link👇) 2. An open-source client you can add into any app How it's built It uses CopilotKit🪁 for the client and interactivity layer, and connects to a 40 line LangGraph ReAct agent that coordinates MCP calls. Hosted on Vercel. Kudos to Suhas Deshpande and Tyler Slaton for hacking and thanks to Harrison Chase for pointers!

Atai Barkai

299,711 views • 1 year ago

🚨🇺🇸 ALAN DERSHOWITZ: THERE IS NO CLIENT LIST, IT NEVER EXISTED “Let's start about the client list. When you say there's a client list, it makes it sound like it's a list drafted or written by Jeffrey Epstein saying, here are the men, in one case, a woman, I lent out people, females, to have sex with. No. There's no such list. It doesn't exist. It never existed." Source: The Dershow

🚨🇺🇸 ALAN DERSHOWITZ: THERE IS NO CLIENT LIST, IT NEVER EXISTED “Let's start about the client list. When you say there's a client list, it makes it sound like it's a list drafted or written by Jeffrey Epstein saying, here are the men, in one case, a woman, I lent out people, females, to have sex with. No. There's no such list. It doesn't exist. It never existed." Source: The Dershow

Mario Nawfal

115,328 views • 1 year ago

No client can say no to you if you learn how to do this. I went from discovery call to finished spanish client deck in under 2 minutes. Here's how I did it: Step 1: Open Claude Step 2: Connect Gmail, Notion, and gammaapp via MCP (one click each, no API keys) Step 3: "Pull the key points from my discovery call notes in Gmail" Step 4: "Grab the client overview from Notion" Step 5: "Build a campaign proposal deck in Gamma using both" A full deck appeared Check here to start:

No client can say no to you if you learn how to do this. I went from discovery call to finished spanish client deck in under 2 minutes. Here's how I did it: Step 1: Open Claude Step 2: Connect Gmail, Notion, and gammaapp via MCP (one click each, no API keys) Step 3: "Pull the key points from my discovery call notes in Gmail" Step 4: "Grab the client overview from Notion" Step 5: "Build a campaign proposal deck in Gamma using both" A full deck appeared Check here to start:

Oluwatimileyin✨🦋

89,017 views • 5 months ago

Lash technician calls the cops and claims a client is trying to run off without paying, then posts the video online. But once people heard what the client had to say, the internet was split, with many saying the situation wasn't as clear-cut as it first seemed.

Lash technician calls the cops and claims a client is trying to run off without paying, then posts the video online. But once people heard what the client had to say, the internet was split, with many saying the situation wasn't as clear-cut as it first seemed.

Chikky

68,070 views • 25 days ago

Roblox has released a Brand New 64-bit Desktop client! it also comes with Byfron's new Anti-Cheat known as Hyperion! With the launch of a 64-bit client, games will also receive small performance boosts. around 1-3% and In certain situations could be >50% What are your thoughts?

Roblox Trading News | Rolimon's

144,953 views • 3 years ago

A returning client reached out to us he wanted to purchase a 2020 GLE 450 We sourced and inspected over 12 vehicles and chose this beautiful amg trim. Brought it in for soft repairs and delivered to the client. Of course we saved him from rubbish(frame 3) 112m spent well✨

A returning client reached out to us he wanted to purchase a 2020 GLE 450 We sourced and inspected over 12 vehicles and chose this beautiful amg trim. Brought it in for soft repairs and delivered to the client. Of course we saved him from rubbish(frame 3) 112m spent well✨

The mechanic

31,909 views • 1 year ago

India should stop chaprification of corporate offices This is so pathetic to see Indian girls dancing in office an d welcoming a foreign client and the becahra client also forced to dance. Such showcasing will only make other countries feel Indian offices are causal and not worthy of serious work.

India should stop chaprification of corporate offices This is so pathetic to see Indian girls dancing in office an d welcoming a foreign client and the becahra client also forced to dance. Such showcasing will only make other countries feel Indian offices are causal and not worthy of serious work.

Woke Eminent

3,752,841 views • 1 year ago

A quick demo of the chart catalog feature on the 3Fourteen Research client site. Along with archives of every report we have ever written, every chart we have ever featured in our research is searchable and available with a link back to the report it was originally featured in on our client site. 3Fourteen Research

A quick demo of the chart catalog feature on the 3Fourteen Research client site. Along with archives of every report we have ever written, every chart we have ever featured in our research is searchable and available with a link back to the report it was originally featured in on our client site. 3Fourteen Research

Fernando Vidal

25,396 views • 1 year ago

You can now connect your React application to any MCP server! And it only takes a single command: $ npx copilotkit@latest init -m MCP This is massive for anyone building React applications! Using the CopilotKit🪁 MCP Client Component, you can get an MCP Client chat component in your application and instant access to any MCP server out there! It doesn't get easier than this. Check out the link below for instructions on how to proceed ↓

You can now connect your React application to any MCP server! And it only takes a single command: $ npx copilotkit@latest init -m MCP This is massive for anyone building React applications! Using the CopilotKit🪁 MCP Client Component, you can get an MCP Client chat component in your application and instant access to any MCP server out there! It doesn't get easier than this. Check out the link below for instructions on how to proceed ↓

Santiago

39,944 views • 1 year ago

Durbin: "In February you made a public claim that the Epstein client list was 'sitting on my desk right now for review.'...Why did you publicly claim to have the Epstein client list waiting for your review and then produce nothing relevant?" Bondi: "I said I had not reviewed it, that it was sitting on my desk...If you see our memo on Epstein clearly points out that there was no client list."

Durbin: "In February you made a public claim that the Epstein client list was 'sitting on my desk right now for review.'...Why did you publicly claim to have the Epstein client list waiting for your review and then produce nothing relevant?" Bondi: "I said I had not reviewed it, that it was sitting on my desk...If you see our memo on Epstein clearly points out that there was no client list."

The Bulwark

129,424 views • 9 months ago