https://www.youtube.com/c/codinginflow
You want to add a shared layout element to some pages in the Next.js app router, but not others. But you don't want to create a nested URL for that.
Solution:
Use route groups to give sibling pages different layouts without changing the URL structure:
You want to add a shared layout element to some pages in the Next.js app router, but not others. But you don't want to create a nested URL for that.
Solution:
Use route groups to give sibling pages different layouts without changing the URL structure:
I want to show a login modal for 401 responses (for any http method)
I want to show a login modal for 401 responses (for any http method)
• implement generateStaticParams to prerender & cache dynamic routes
• if you can't prerender the page, use suspense boundaries
• lazy-load heavy NPM packages client-side with `dynamic`
• use next/Font & next/Image
• implement generateStaticParams to prerender & cache dynamic routes
• if you can't prerender the page, use suspense boundaries
• lazy-load heavy NPM packages client-side with `dynamic`
• use next/Font & next/Image
This can make it tedious to style article pages from scratch. Like blog posts with different headlines, links, paragraphs, etc.
Tip: Install tailwind-prose to get beautiful default styling for your articles 👇
This can make it tedious to style article pages from scratch. Like blog posts with different headlines, links, paragraphs, etc.
Tip: Install tailwind-prose to get beautiful default styling for your articles 👇
Each tab is a page and with staleTimes: 30 they are cached client-side for 30 seconds.
Each tab is a page and with staleTimes: 30 they are cached client-side for 30 seconds.
This naming convention is necessary because hooks are special functions that have to follow certain rules.
This naming convention is necessary because hooks are special functions that have to follow certain rules.
but yet you never useBrain
but yet you never useBrain
Nooothing to worry about
Nooothing to worry about
The language is so bad that it's like being thrown in cold water. After that, it's all uphill.
The language is so bad that it's like being thrown in cold water. After that, it's all uphill.
If you want to reset the state of a component, you should use it too.
But attention, you want to put the key in a wrapper component so your callers don't have to remember it.
Here is how 👇
If you want to reset the state of a component, you should use it too.
But attention, you want to put the key in a wrapper component so your callers don't have to remember it.
Here is how 👇
- new syntax
- new use() hook
- industry best practices
(YT link in 1st reply)
- new syntax
- new use() hook
- industry best practices
(YT link in 1st reply)
Tip: You shouldn't use @apply
Tip: You shouldn't use @apply
(code in first reply)
(code in first reply)