nextjs
dz / webdev / nextjsSummary
Things related to the next.js framework
Node Tree
- network_boundary
- typescript_plugin
- partial_rendering
- root_layout
- vercel_postgres
- route_handler
- RSC_payload
- fast_refresh
- learn_dashboard_app
Nodes
| learn_dashboard_app | |
| content | Tutorial for how to make a full-stack web application with next.js |
| children | webdev/clsx (clsx library used in nextjs dashboard tutorial), partial_rendering_ex (mentioned in dashboard app tutorial), react_foundations (suggested prereq course before dashboard app) |
| hyperlink | https://nextjs.org/learn/dashboard-app |
| react_foundations | |
| content | React Foundations course |
| parents | learn_dashboard_app |
| hyperlink | https://nextjs.org/learn/react-foundations |
| network_boundary | |
| content | Network Boundary: a conceptual line that separates the server and client environments |
| hyperlink | https://nextjs.org/learn/react-foundations/server-and-client-components#network-boundary |
| flashcard (front) | What is a network boundary? |
| flashcard (back) | A conceptual line that separtes the server and client environments |
| RSC_payload | |
| content | RSC Payload: The React Server Component Payload is a special data format that contains the rendered results of the server components, as well as placeholders where client components should be rendered and their javascript files. It is sent to the client. |
| flashcard (front) | What is an RSC payload? |
| flashcard (back) | The React Server Component (RSC) payload is a data format sent to the client in a NextJS setup. It represents the the rendered results of the server components, and has placeholders for the client components. |
| fast_refresh | |
| content | fast refresh: React feature integrate into Next.js that allows you to live reload the browser page while maintaining temporary client-side state when you save changes to a file. |
| hyperlink | https://nextjs.org/docs/architecture/fast-refresh |
| typescript_plugin | |
| content | typescript plugin for nextjs |
| hyperlink | https://nextjs.org/docs/app/building-your-application/configuring/typescript#typescript-plugin |
| partial_rendering | |
| content | partial rendering: only the route segments that change on navigation re-render on the client, and any shared segments are preserved. |
| children | partial_rendering_ex (example) |
| hyperlink | https://nextjs.org/docs/app/building-your-application/routing/linking-and-navigating#4-partial-rendering |
| flashcard (front) | What is partial rendering? |
| flashcard (back) | In NextJS, partial rendering occurs in the context of navigation. Only segments that change on navigation re-render on the client. Any shared segments are preserved. |
| partial_rendering_ex | |
| content | Ex: when navigating between sibling routes that have a shared layout such as =/dashboard/settings= and =/dashboard/analytics=, only the individual pages will be rendered. |
| parents | partial_rendering, learn_dashboard_app |
| root_layout | |
| content | root layout: required. placed at top-level of your app. must contain =<html>= and =<body>= tags. |
| hyperlink | https://nextjs.org/docs/app/building-your-application/routing/layouts-and-templates#root-layout-required |
| vercel_postgres | |
| content | Vercel Postgres SDK |
| hyperlink | https://vercel.com/docs/storage/vercel-postgres/sdk |
| route_handler | |
| content | Route Handlers: allow you to create custom request handlers for a given route using the Web Request and Response APIs |
| children | webdev/request_api (route handlers use the request API to make,custom requests for the given route), webdev/response_api (route handlers use the response API to make,custom requests for the given route) |
| hyperlink | https://nextjs.org/docs/app/building-your-application/routing/route-handlers |
| flashcard (front) | What is a route handler? |
| flashcard (back) | Route handlers in NextJS enable the creation of custom request handlers for a given route. |