Next.js from Development to Deployment - getServerSideProps and getStaticProps

The video tutorial covers three data fetching methods provided by Next.js: getServerSideProps, getStaticProps, and getStaticPaths. It explains how each method works, their use cases, and how to implement them in a Next.js project. The tutorial also discusses setting up API URLs and environment variables for data fetching. Additionally, it demonstrates how to fetch data for a homepage and handle dynamic routes using getStaticPaths.

Which method in Next.js fetches data on each request?

• useEffect

• getStaticPaths

• getServerSideProps

• getStaticProps

What is the role of getStaticPaths in Next.js?

• To manage state

• To fetch data on each request

• To create dynamic routes

• To handle client-side rendering

What is a limitation of using Next.js API routes for static site generation?

• They cannot handle dynamic routes

• They do not support third-party APIs

• They cannot generate static websites

• They are slower than server-side rendering

What is the purpose of setting an environment variable for the API URL?

• To enable caching

• To improve server performance

• To make it visible within the client

• To secure the API endpoint

What does getStaticProps do at build time?

• Fetches data on each request

• Makes a request and builds static pages

• Updates data in real-time

• Generates dynamic routes

How can you handle data updates with getStaticProps?

• By setting a timeout

• By using getServerSideProps

• By adding a revalidate option

• By using useEffect

Why might you choose getServerSideProps over getStaticProps?

• To handle real-time data updates

• To reduce server load

• For faster build times

• To fetch data at build time