I'm glad to hear that you found the error correction process helpful! It's important to demonstrate how to troubleshoot and fix issues that may arise during implementation. If you have any more questions or need further clarification on anything, feel free to ask. Don't forget to like, share, and subscribe for more helpful content. Also, click the bell icon for updates and visit ayyaztech.com for additional tutorials. Your support is greatly appreciated! 😊👍
Thank you so much for your kind words! I'm really glad the video helped you 😊. If you're diving deeper into Next.js 14 or Mongoose, here are some additional resources you might find useful: - How to use SWR in Next js 14 APP directory? ruclips.net/video/49VN7JNmK7U/видео.html - Learn How to Create a REST API Using Next.js 14's New App Directory Structure ruclips.net/video/q94GIKLmPBI/видео.html Also, feel free to check out my blog for more tutorials. Here’s one that might interest you: - Creating an API with Node.js: A Step-by-Step Tutorial www.ayyaztech.com/blog/creating-an-api-with-nodejs-a-step-by-step-tutorial Don't forget to like, share, and subscribe for more content, and hit the bell icon for notifications 🔔!
What if I want to compile all models at once? Like, for relationship fields. Do I make an entire file just for compiling the models or the application will auto-compile all the models if each of them has an route handler?
Thank you for your comment! I appreciate your input. Could you please provide more details or clarify what you mean by 'new keyboard instead model making'? I'd love to understand your suggestion better so I can improve the content or explore different approaches. Thanks again
I particularly liked your showing the process of error correction after implementing. So much useful information in a short video
I'm glad to hear that you found the error correction process helpful! It's important to demonstrate how to troubleshoot and fix issues that may arise during implementation. If you have any more questions or need further clarification on anything, feel free to ask. Don't forget to like, share, and subscribe for more helpful content. Also, click the bell icon for updates and visit ayyaztech.com for additional tutorials. Your support is greatly appreciated! 😊👍
I'm Brazilian and I really needed this video, thank you very much
Thank you so much for your kind words! I'm really glad the video helped you 😊. If you're diving deeper into Next.js 14 or Mongoose, here are some additional resources you might find useful:
- How to use SWR in Next js 14 APP directory?
ruclips.net/video/49VN7JNmK7U/видео.html
- Learn How to Create a REST API Using Next.js 14's New App Directory Structure
ruclips.net/video/q94GIKLmPBI/видео.html
Also, feel free to check out my blog for more tutorials. Here’s one that might interest you:
- Creating an API with Node.js: A Step-by-Step Tutorial
www.ayyaztech.com/blog/creating-an-api-with-nodejs-a-step-by-step-tutorial
Don't forget to like, share, and subscribe for more content, and hit the bell icon for notifications 🔔!
Nice Video
but sir, repo ma code share kar diya kare.
please make build of project also
What if I want to compile all models at once? Like, for relationship fields. Do I make an entire file just for compiling the models or the application will auto-compile all the models if each of them has an route handler?
This type of model seems for api..? If i want to make simple app then follow the downwards code only.. isn't it...?
Very Nice video.. But the way you have checked if mongoose.models.ModelName || model.. this is not typesafe.. it return mongoose model = any type.
Whats the best way to check?
@@GospelMessageTV You should specify type in model generic.
how can i define name of database (like here it is test) how and where can i define it
using nextjs 14
In the creation of a database, or mongoose schema
Thank you so much
vercel deploy error
mongoose doesn't support edge time
@@prashant-yr1re in that case what should do to fix it?
@@FauroOficial use prisma as adaptor
Use new keyboard instead model making
Thank you for your comment! I appreciate your input. Could you please provide more details or clarify what you mean by 'new keyboard instead model making'? I'd love to understand your suggestion better so I can improve the content or explore different approaches. Thanks again
bruh you talk to much get strait to the point