This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.js. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

Learn More

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

CHAPTER 1, 2, 3

Routing

• File-based route
• Nested route
• Dynamic rout
• Catch-all route

Link

• element, the network fetches only a small Javascript file needed for that route.

• element, the browser reloads the entire web applications.

• Each route (or folder) in your application should have a page.js file that exports a default component. This component will be used as the UI for that route.

• The layout.js file inside /app folder is a shared UI that shapes the layout of your application. You can place components that are used in all routes in this file.

CHAPTER 4 - SERVER AND CLIENT COMPONENTS

• All components created in Next.js are server components by default. The Javascript bundle size can be minimized and the application will load faster.

• A server component is also SEO-friendly because search engine bots will be able to see the content of the page.

• Why use client components if server components are that good? Because the main drawback of server components is interactivity. A server component can't listen to browser events such as a click , a form submission and changes on an input field.

• Recomment to create a client component in a seperate file, and then import the client component to the server component.

CHAPTER 5 - SERVER ACTIONS AND DATA FETCHING

• A server action is an asynchronous function that's executed on the server, but it can be called both from server and client components.

• A server action is private, so you don't need to create dedicated API routes to run code that should be hidden from the client, like updating the database and fetching external API with secrect keys.

When to use server actions?

• Sending requests to external APIs
• Manipulating database records (CRUD)
• Performing business logic such as validating submitted data and processing payments.

CHAPTER 10

• Under the hood, NextAuth creates a session that holds information about the user after authencation. You can use the getServerSession() function provided by NextAuth.

• To retrieve session data from the client, NextAuth provides a component, which uses React Context under the hood, and the useSession() hook to get data stored in that context and the status (authenticated/ unauthenticated).

• useSession() can called update() function to update the session data in User.Form.js

API route

NextAuth session object:

authorize() in authConfig.js will return the value object that will be added to the session object

http://localhost:3000/api/auth/session

{
    user: {
        name: string
        email: string
        image: string
    },
    expires: Date // This is the expiry of the session
}


{
    "user": {
        "name": "bidewa",
        "email": "bidewa1989@gmail.com",
        "image": "https://utfs.io/f/82mbOgadxuNmy5J0f8jE7TvGK6XSiReaComMVJZ8Ln90bgBA"
    },
    "expires": "2024-10-30T04:19:16.175Z"
}

2. Uploadthing

http://localhost:3000/api/uploadthing [ { "slug": "imageUploader", "config": { "image": { "maxFileSize": "4MB", "maxFileCount": 1, "minFileCount": 1, "contentDisposition": "inline" } } } ]

CHAPER 13 - CREATE EVENT

// http://localhost:3000/events/create

[ "66f380549982945954306da3", { "startDateTime": "$D2024-09-30T08:26:07.160Z", "endDateTime": "$D2024-09-30T08:26:07.160Z", "title": "Iphone 16", "category": "Technology", "location": "Ho Chi Minh", "url": "https://www.google.com", "description": "Introduction about new Iphone 16", "endDatetime": "$D2024-10-01T08:30:00.000Z", "imageUrl": "https://utfs.io/f/82mbOgadxuNmvzxcnhp6rKHy7Pv0pfiSXqC14hQ5OGknUM9j" }, "/profile" ]

CHAPTER 14 - UPDATE EVENT

http://localhost:3000/events/66fa61a78d72b25728ac25a9/update

Payload: [ { "userId": "66f380549982945954306da3", "event": { "_id": "66fa61a78d72b25728ac25a9", "title": "Iphone 16", "description": "Introduction about new Iphone 16 (updated event)", "location": "Ho Chi Minh", "imageUrl": "https://utfs.io/f/82mbOgadxuNmvzxcnhp6rKHy7Pv0pfiSXqC14hQ5OGknUM9j", "startDateTime": "$D2024-09-30T08:26:07.160Z", "endDateTime": "$D2024-09-30T08:26:07.160Z", "url": "https://www.google.com", "category": "Technology", "organizer": { "_id": "66f380549982945954306da3", "name": "bidewa" }, "createdAt": "2024-09-30T08:30:31.502Z", "__v": 0, "endDatetime": "$D2024-10-22T17:00:00.000Z" }, "path": "/events/66fa61a78d72b25728ac25a9" } ]