#80daysofnextjs search results
day 79 - discovered Next.js enforces a 1MB file upload limit for Server Actions - makes sense - prevents overload/crashes (cos uploads are buffered) - can increase the limit in next.config.js (handy for small/medium size uploads) #80DaysOfNextJS #NextJS15 #React #TypeScript
day 72 - paired Server Actions with useFormStatus() hook in Next.js 15 - the hook exposes a 'pending' Boolean during form submision - perfect for disabling the submit button or showing feedback like "submitting" simple but good UX #80DaysOfNextJS #NextJS15 #React #TypeScript
day 73 - tried server-side validation + error handling in forms using Server Actions + useActionState() hook in Next.js15 - the hook gives you 1 form state 2 formAction(trigger) 3. isPending (boolean for loading) - basically all you need for form handling #80DaysOfNextJS
day 71 - got hands-on with Server Actions in Next.js 15 - created and styled a simple form to add an animal item to the DB - no messy state management - no manual API routes setup - just a single async function.... #80DaysOfNextJS #NextJS15 #React #TypeScript
day 74 - implemented update functionality using Server Actions - created & styled edit form - defined Prisma DB helper func and Server Action to handle actual update #80DaysOfNextJS #NextJS15 #React #TypeScript
day 76 - tried delete operation with Server Actions + useOptimistic() hook in Next.js15 - the hook lets the UI update instantly while the async delete request is pending - no waiting for server response #80DaysOfNextJS #NextJS15 #React #TypeScript
day 77 - learned its best practice to move Server Action functions into their own dedicated file - place 'use server' directive at top of the file and boom - every function in there is treated as a Server Action #80DaysOfNextJS #NextJS15 #React #TypeScript
- added server-side validation & error handling with useActionState() hook - errors display directly in the form UI - also learned how to pass additional arguments to a Server Action with .bind() am I Server Action Guru yet? #80DaysOfNextJS #NextJS15 #React #TypeScript
day 78 - experimented with multipart forms (file uploads) using Server Actions in Next.js - refactored my 'createAnimal' Server Action (saves animal item to DB) to now accept image uploads ( feels much more flexible & realistic) #80DaysOfNextJS #NextJS15 #React #TypeScript
day 75 - delete operation with Server Action in Next.js15 - wrapped delete button in a <form> and hooked it directly to the server action (a neat/clever hack) - used .bind() method to pass id to action clean w minimal boilerplate #80DaysOfNextJS #NextJS15 #React #TypeScrip
day 80 - GitHub repo with all the code, concepts, and implementations from my #80DaysOfNextJS challenge👉 github.com/Coding-Robin00… - gave myself a pat on the back - learned a lot & definitely leveled up as a software engineer/dev #80DaysOfNextJS #NextJS15 #TypeScript
-cleaner, modular, testable call me captain obvious #80DaysOfNextJS #NextJS15 #React #TypeScript
- works great for small/medium file uploads but ran into some 'Error: Body exceeded limit' issues - curious to see how it behaves with much larger uploads hmm🤔 #80DaysOfNextJS #NextJS15 #React #TypeScript
- love how Server Actions build on the concept of direct db access from server components - write helper functions to query/mutate data, then use Server Actions to safely expose them to client its smart and effective #80DaysOfNextJS #NextJS15 #React #TypeScript
- added validation & error handlin (if no file or file > 3mb -> return error) - upload process -> create upload dir (if missin), convert file obj to buffer, save to /public/uploads and finally generate public URL for Next to serve #80DaysOfNextJS #NextJS15 #React #TypeScript
- rewarded myself with small chicken + ice cream- na the real motivation be that 😎 - super proud of me... I feel limitless! do am if e easy😏 #80DaysOfNextJS #NextJS15 #TypeScript
- but for large uploads (videos/high resolution images) external solutions like Cloudinary is the way to go cool #80DaysOfNextJS #NextJS15 #React #TypeScript
-just a single async function marked with 'use server' dispatching my prisma DB helper function - flow is like : form -> server action -> DB -> redirect very clean and super convenient #80DaysOfNextJS #NextJS15 #React #TypeScript
- implementation also intuitive - just filter the deleted item out of the array - makes the UI extra smooth but in larger datasets it could cause sync issues if you dont revalidate - good UX but feels a bit like an overkill - especially for small apps #80DaysOfNextJS #NextJS15
- errors are returned directly from server -> form state -> form UI -- smooth UX - tradeoff: entire form component must be marked 'use client', making it client-rendered - good trade-off? still deciding....🤔 #80DaysOfNextJS #NextJS15 #React #TypeScript
- rewarded myself with small chicken + ice cream- na the real motivation be that 😎 - super proud of me... I feel limitless! do am if e easy😏 #80DaysOfNextJS #NextJS15 #TypeScript
day 80 - GitHub repo with all the code, concepts, and implementations from my #80DaysOfNextJS challenge👉 github.com/Coding-Robin00… - gave myself a pat on the back - learned a lot & definitely leveled up as a software engineer/dev #80DaysOfNextJS #NextJS15 #TypeScript
- but for large uploads (videos/high resolution images) external solutions like Cloudinary is the way to go cool #80DaysOfNextJS #NextJS15 #React #TypeScript
day 79 - discovered Next.js enforces a 1MB file upload limit for Server Actions - makes sense - prevents overload/crashes (cos uploads are buffered) - can increase the limit in next.config.js (handy for small/medium size uploads) #80DaysOfNextJS #NextJS15 #React #TypeScript
- works great for small/medium file uploads but ran into some 'Error: Body exceeded limit' issues - curious to see how it behaves with much larger uploads hmm🤔 #80DaysOfNextJS #NextJS15 #React #TypeScript
- added validation & error handlin (if no file or file > 3mb -> return error) - upload process -> create upload dir (if missin), convert file obj to buffer, save to /public/uploads and finally generate public URL for Next to serve #80DaysOfNextJS #NextJS15 #React #TypeScript
day 78 - experimented with multipart forms (file uploads) using Server Actions in Next.js - refactored my 'createAnimal' Server Action (saves animal item to DB) to now accept image uploads ( feels much more flexible & realistic) #80DaysOfNextJS #NextJS15 #React #TypeScript
-cleaner, modular, testable call me captain obvious #80DaysOfNextJS #NextJS15 #React #TypeScript
day 77 - learned its best practice to move Server Action functions into their own dedicated file - place 'use server' directive at top of the file and boom - every function in there is treated as a Server Action #80DaysOfNextJS #NextJS15 #React #TypeScript
- implementation also intuitive - just filter the deleted item out of the array - makes the UI extra smooth but in larger datasets it could cause sync issues if you dont revalidate - good UX but feels a bit like an overkill - especially for small apps #80DaysOfNextJS #NextJS15
day 76 - tried delete operation with Server Actions + useOptimistic() hook in Next.js15 - the hook lets the UI update instantly while the async delete request is pending - no waiting for server response #80DaysOfNextJS #NextJS15 #React #TypeScript
day 75 - delete operation with Server Action in Next.js15 - wrapped delete button in a <form> and hooked it directly to the server action (a neat/clever hack) - used .bind() method to pass id to action clean w minimal boilerplate #80DaysOfNextJS #NextJS15 #React #TypeScrip
- added server-side validation & error handling with useActionState() hook - errors display directly in the form UI - also learned how to pass additional arguments to a Server Action with .bind() am I Server Action Guru yet? #80DaysOfNextJS #NextJS15 #React #TypeScript
day 74 - implemented update functionality using Server Actions - created & styled edit form - defined Prisma DB helper func and Server Action to handle actual update #80DaysOfNextJS #NextJS15 #React #TypeScript
- errors are returned directly from server -> form state -> form UI -- smooth UX - tradeoff: entire form component must be marked 'use client', making it client-rendered - good trade-off? still deciding....🤔 #80DaysOfNextJS #NextJS15 #React #TypeScript
day 73 - tried server-side validation + error handling in forms using Server Actions + useActionState() hook in Next.js15 - the hook gives you 1 form state 2 formAction(trigger) 3. isPending (boolean for loading) - basically all you need for form handling #80DaysOfNextJS
day 72 - paired Server Actions with useFormStatus() hook in Next.js 15 - the hook exposes a 'pending' Boolean during form submision - perfect for disabling the submit button or showing feedback like "submitting" simple but good UX #80DaysOfNextJS #NextJS15 #React #TypeScript
-just a single async function marked with 'use server' dispatching my prisma DB helper function - flow is like : form -> server action -> DB -> redirect very clean and super convenient #80DaysOfNextJS #NextJS15 #React #TypeScript
day 71 - got hands-on with Server Actions in Next.js 15 - created and styled a simple form to add an animal item to the DB - no messy state management - no manual API routes setup - just a single async function.... #80DaysOfNextJS #NextJS15 #React #TypeScript
- love how Server Actions build on the concept of direct db access from server components - write helper functions to query/mutate data, then use Server Actions to safely expose them to client its smart and effective #80DaysOfNextJS #NextJS15 #React #TypeScript
day 74 - implemented update functionality using Server Actions - created & styled edit form - defined Prisma DB helper func and Server Action to handle actual update #80DaysOfNextJS #NextJS15 #React #TypeScript
day 79 - discovered Next.js enforces a 1MB file upload limit for Server Actions - makes sense - prevents overload/crashes (cos uploads are buffered) - can increase the limit in next.config.js (handy for small/medium size uploads) #80DaysOfNextJS #NextJS15 #React #TypeScript
day 72 - paired Server Actions with useFormStatus() hook in Next.js 15 - the hook exposes a 'pending' Boolean during form submision - perfect for disabling the submit button or showing feedback like "submitting" simple but good UX #80DaysOfNextJS #NextJS15 #React #TypeScript
day 73 - tried server-side validation + error handling in forms using Server Actions + useActionState() hook in Next.js15 - the hook gives you 1 form state 2 formAction(trigger) 3. isPending (boolean for loading) - basically all you need for form handling #80DaysOfNextJS
day 76 - tried delete operation with Server Actions + useOptimistic() hook in Next.js15 - the hook lets the UI update instantly while the async delete request is pending - no waiting for server response #80DaysOfNextJS #NextJS15 #React #TypeScript
day 75 - delete operation with Server Action in Next.js15 - wrapped delete button in a <form> and hooked it directly to the server action (a neat/clever hack) - used .bind() method to pass id to action clean w minimal boilerplate #80DaysOfNextJS #NextJS15 #React #TypeScrip
day 78 - experimented with multipart forms (file uploads) using Server Actions in Next.js - refactored my 'createAnimal' Server Action (saves animal item to DB) to now accept image uploads ( feels much more flexible & realistic) #80DaysOfNextJS #NextJS15 #React #TypeScript
day 77 - learned its best practice to move Server Action functions into their own dedicated file - place 'use server' directive at top of the file and boom - every function in there is treated as a Server Action #80DaysOfNextJS #NextJS15 #React #TypeScript
day 69 -took a deeper dive into direct DB communications from server components in Next.js 15 - setup Prisma (ORM) + SQLite (DB) in my app - defined a basic Animal model schema and seeded some initial data #80DaysOfNextJS #NextJS15 #React #TypeScript
- built some simple helper funcs(queries & mutations) to handle CRUD operations - fetched data straight from the DB and rendered a simple animal list UI very satisfying to see it action! wow! #80DaysOfNextJS #NextJS15 #React #TypeScript
day 63 - dived into Sequential Data Fetching in Next.js15 - basically when one request depends on another (fetch B needs data from fetch A) - slower (longer loading) but sometimes you just cannot avoid it #80DaysOfNextJS #NextJS15 #React #typeScript
day 71 - got hands-on with Server Actions in Next.js 15 - created and styled a simple form to add an animal item to the DB - no messy state management - no manual API routes setup - just a single async function.... #80DaysOfNextJS #NextJS15 #React #TypeScript
- unknown errors still bubbles up to Error.tsx for safety - states ( loading/success/error ) all isolated per component - feels smoother with a more reliable UX cool #80DaysOfNextJS #NextJS15 #React
- added server-side validation & error handling with useActionState() hook - errors display directly in the form UI - also learned how to pass additional arguments to a Server Action with .bind() am I Server Action Guru yet? #80DaysOfNextJS #NextJS15 #React #TypeScript
day 66 - tried Parallel Fetching + Suspense + Try/Catch error-handling (Next.js15) - posts & albums load side by side (parallel), each with its own fallback - errors handled locally (with try/catch) → page stays intact, no “forever loading” states #80DaysOfNextJS #NextJS15
- parent just renders two Suspense boundaries -- both children fetch in parallel ( same time ) - each streams in when ready without blocking the UI - result: cleaner code + non-blocking UI + easy to reason about #80DaysOfNextJS #NextJS15 #React #typeScript
day67 - Parallel fetching + Suspense + try/catch + client-side retry (Next.js15) - userPosts & userAlbums load independently - has own fallbacks and handles own data fetching, loading, local error state - added Retry button... #80DaysOfNextJS #NextJS15 #React #TypeScript
day 65 - experimented with parallel data fetching + suspense fallbacks (Next.js15) - each child component ( userPost.tsx, userAlbum.tsx ) handles own async data fetching instead of resolving everything in parent #80DaysOfNextJS #NextJS15 #React #typeScript
Day 64 - played around with Parallel Data fetching (basically the opposite of Sequential) - multiple requests start at the same time = faster loading overall - if fetch A fails, fetch B can still succeed (really cool) #80DaysOfNextJS #NextJS15 #React #typeScript
- e.g. fetch all posts → then for each post, fetch author using userId - classic “one after the other” pattern - downside: if fetch A fails, fetch B does not even start #80DaysOfNextJS #NextJS15 #React #typeScript
Something went wrong.
Something went wrong.
United States Trends
- 1. #Worlds2025 42.3K posts
- 2. Doran 17.1K posts
- 3. #T1WIN 27.6K posts
- 4. Sam Houston 1,608 posts
- 5. Oregon State 4,717 posts
- 6. Boots 29K posts
- 7. Faker 31.2K posts
- 8. Lubin 5,838 posts
- 9. Keria 10.7K posts
- 10. #T1fighting 3,421 posts
- 11. #Toonami 2,728 posts
- 12. Option 2 4,166 posts
- 13. #GoAvsGo 1,605 posts
- 14. Hyan 1,414 posts
- 15. Louisville 14.3K posts
- 16. Frankenstein 125K posts
- 17. Oilers 5,334 posts
- 18. UCLA 7,786 posts
- 19. Nuss 5,613 posts
- 20. PETE DAVIDSON N/A