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.

Next.js 15: <Form> • Prefetching • Client-side navigation • Progressive enhancement It is useful for forms that navigate to a new page, such as a search form that leads to a results page.

Delba

53,275 subscribers

67,908 views • 2 years ago •via X (Twitter)

Science & Technology Education

Anya Rossi• Live Now

Private livecam show

10 Comments

Delba2 years ago

🚀 by @lubieowoce

henrique cunha2 years ago

delba, please release your remotion setup 🙏

Sidi jeddou2 years ago

This is amazing, Delba. I’m not sure if I should upgrade to v15 for I’m scared😅

Delba2 years ago

Up to you. Some folks like to wait a bit. If it helps, we've had two RCs and use v15 on all Vercel sites. If you do, try running the upgrade CLI with automated codemods for every change. Let us know if it missed anything.

Matt2 years ago

Love these vids every time Delba 🙏🏼

freddie2 years ago

i could swear i’ve seen this API before

Vitaly Gashkov2 years ago

What color theme is this? 🤔

Indra Zulfi🧢2 years ago

Hey @delba_oliveira Thanks for Sharing. Quick qs, How do you build this kind of video?

Prabhas2 years ago

Great explanation with cool animation

Andrew Aliaj2 years ago

another cool feature by Next.js

Related Videos

Let's build an email client with Next.js and Postgres ✉️ ✅ Navigate between routes in a column layout while maintaining scroll position (layouts support) ✅ Submit forms without JavaScript enabled (progressive enhancement) ✅ Navigate between routes extremely fast (prefetching and caching) ✅ Retain your UI position on reload (URL state)

Let's build an email client with Next.js and Postgres ✉️ ✅ Navigate between routes in a column layout while maintaining scroll position (layouts support) ✅ Submit forms without JavaScript enabled (progressive enhancement) ✅ Navigate between routes extremely fast (prefetching and caching) ✅ Retain your UI position on reload (URL state)

Lee Robinson

197,036 views • 3 years ago

Clutch is a great way to find leads. I just built a free tool that will scrape the search results page for you. Get tens of thousands of results in a few minutes. Drop a comment to get it 🔥

Clutch is a great way to find leads. I just built a free tool that will scrape the search results page for you. Get tens of thousands of results in a few minutes. Drop a comment to get it 🔥

Adrian | The Web Scraping Guy

24,406 views • 2 years ago

How to use Next.js metadata if the page is a client component

How to use Next.js metadata if the page is a client component

Alex Sidorenko

91,579 views • 2 years ago

Next.js preserves client state on the page during navigation when cacheComponents is enabled

Next.js preserves client state on the page during navigation when cacheComponents is enabled

Alex Sidorenko

161,709 views • 11 months ago

Form validation is hard. What if there was a Next.js form lib that does both client and server validation from one Zod schema 👀

Form validation is hard. What if there was a Next.js form lib that does both client and server validation from one Zod schema 👀

Alex Sidorenko

145,980 views • 2 years ago

Wanna see something wild? This is a search-as-you-type that uses navigate() on every keypress. Keeps all important state in the URL. Page reload and browser navigation always works. thanks to TanStack Router 🤘

Wanna see something wild? This is a search-as-you-type that uses navigate() on every keypress. Keeps all important state in the URL. Page reload and browser navigation always works. thanks to TanStack Router 🤘

Swizec Teller

102,500 views • 2 years ago

Search box with next/form in Next.js 15

Search box with next/form in Next.js 15

Alex Sidorenko

86,436 views • 2 years ago

A navigation to a dynamic server-rendered page is blocked until the server responds. In Next.js, the first step to improving the experience is to add a `loading.js` file. This unblocks navigation and gives the user feedback while the content streams in.

A navigation to a dynamic server-rendered page is blocked until the server responds. In Next.js, the first step to improving the experience is to add a `loading.js` file. This unblocks navigation and gives the user feedback while the content streams in.

Delba

50,434 views • 1 year ago

This is a fully dynamic, server-rendered Next.js app router + headless Shopify storefront. Zero client / CDN page caches, fully personalized, feels as though it was local-first. Try it for yourself!

This is a fully dynamic, server-rendered Next.js app router + headless Shopify storefront. Zero client / CDN page caches, fully personalized, feels as though it was local-first. Try it for yourself!

Guillermo Rauch

66,022 views • 2 years ago

LIVE UPDATE: A man at the INEC office has alleged that officials are giving people Death Certificate forms to fill and sign, while presenting them as Voter Registration forms. We are being asked to fill and sign what is clearly a Death Certificate form, but they are calling it a voters’ registration form,” the man said.🗣️

LIVE UPDATE: A man at the INEC office has alleged that officials are giving people Death Certificate forms to fill and sign, while presenting them as Voter Registration forms. We are being asked to fill and sign what is clearly a Death Certificate form, but they are calling it a voters’ registration form,” the man said.🗣️

Big Sman.🍥

145,500 views • 4 months ago

How should you search, filter, and paginate data with Next.js? This demo has 50,000 books in a Postgres database. • Page Load: When the page loads, we see the React Suspense fallback. This loading skeleton is displayed until the first page of books is retrieved from the database. • Searching: The search input has a 200ms debounce. After 200ms of inactivity, the form submits, updating the URL state with `?q={search}`. The Server Component reads `searchParams` and queries the database. On form submission, a React transition starts, allowing us to read the pending status with `useFormStatus` to display an inline loading state. • State Preservation: Navigating to an individual book page retains the search input state. Reloading the page or sharing the link preserves the search results. • Client-side Filtering: Filtering authors in the left sidebar is done client-side. Authors are fetched by a Server Component and passed as props to the sidebar. Changing the input value updates React state and re-renders the sidebar. • Optimistic Updates: The sidebar’s selected authors are optimistically updated with `useOptimistic`. Checkbox selections update instantly without waiting for the URL to change. • State Preservation: Navigating to an individual book page retains the sidebar filter input and selected author state across navigations, giving it an app-like feel. • Pagination: Navigating between pages updates the URL state, triggering the Server Component to query the database for the specific page of books. We also fetch the total book count to show the total number of pages. This demo isn't perfect yet (still working on it) but it's been a fun playground for some of these patterns. You can imagine a similar experience for thousands of movies, cars, products, or any other very large dataset. Demo → Code →

How should you search, filter, and paginate data with Next.js? This demo has 50,000 books in a Postgres database. • Page Load: When the page loads, we see the React Suspense fallback. This loading skeleton is displayed until the first page of books is retrieved from the database. • Searching: The search input has a 200ms debounce. After 200ms of inactivity, the form submits, updating the URL state with `?q={search}`. The Server Component reads `searchParams` and queries the database. On form submission, a React transition starts, allowing us to read the pending status with `useFormStatus` to display an inline loading state. • State Preservation: Navigating to an individual book page retains the search input state. Reloading the page or sharing the link preserves the search results. • Client-side Filtering: Filtering authors in the left sidebar is done client-side. Authors are fetched by a Server Component and passed as props to the sidebar. Changing the input value updates React state and re-renders the sidebar. • Optimistic Updates: The sidebar’s selected authors are optimistically updated with `useOptimistic`. Checkbox selections update instantly without waiting for the URL to change. • State Preservation: Navigating to an individual book page retains the sidebar filter input and selected author state across navigations, giving it an app-like feel. • Pagination: Navigating between pages updates the URL state, triggering the Server Component to query the database for the specific page of books. We also fetch the total book count to show the total number of pages. This demo isn't perfect yet (still working on it) but it's been a fun playground for some of these patterns. You can imagine a similar experience for thousands of movies, cars, products, or any other very large dataset. Demo → Code →

Lee Robinson

237,080 views • 2 years ago

The fact that you can deeply connect with a character form a side quest, help them out and still have the option to give into hunger is such a wild feature to have

The fact that you can deeply connect with a character form a side quest, help them out and still have the option to give into hunger is such a wild feature to have

NikTek

50,492 views • 1 month ago

Server-side form validation in Next.js

Server-side form validation in Next.js

Alex Sidorenko

72,160 views • 2 years ago

You absolutely have to watch this. The new federal standards require a loyalty pledge in the form of a two page essay to the dictatorship.

You absolutely have to watch this. The new federal standards require a loyalty pledge in the form of a two page essay to the dictatorship.

MAGA Cult Slayer

30,124 views • 1 year ago