Thanks for the tutorial! I’m currently migrating my current live portfolio (already with firebase) from basic html/css/js to nextjs/tailwind. I have a question: so I just need to select the "Use an existing project" option (which is my live portfolio) to deploy the new nextjs portfolio? And would the files of my old portfolio be automatically fully replaced?
Hello guys, I have the same problem. I discovered that occurs because the default req for next server contains _next in the url, and firebase doesn't support this. There's some tutorials on the web teaching how to configure, but just older versions of Next. Can you guys solved the problem?@@tsykin
Great tutorial! thanks. Just one question, do you know if all the features from Next.js, like server side components/functions and etc are available when using Firebase hosting? I did read somewhere that a Node.js server is needed for that, but I don't have a clue of how Firebase hosting works.
Thanks for feedback. I am yet to test deployment of an app with advanced functionality, so I might come back with information on that. For now it's up to you to use my tutorial to test out those features 😊
Of course using hosting platform is faster and easier. But it's also pricy and sometimes lacks ability to go inside the machine that hosts your app. That's why I showed how to host you Next.js app for free on a VM 😊 And yes, you might need to add credit card details to Google Cloud when setting this up, but you won't be charged anything if done correctly.
Normal pages are loading fine, But when I deploy nextjs project with dynamic pages I'm getting error like this. Building a Cloud Function to run this application. This is needed due to: • non-static component /todos/[id]/page Unable to bundle next.config.js for use in Cloud Functions, proceeding with deploy but problems may be enountered. The command line is too long. How can solve this issue?
Thanks for reporting this. To be honest I am a beginner developer and I have not encountered this issue. Hopefully someone more experienced will reply to your comment.
the enable experimental webframeworks is a life saver. i debugged for so many hours but this setting finally automated the deploy process
Glad my guide helped you 👍
Great tutorial, appreciate you taking the time and step by step guide, worked perfectly for me 🙏
I am really glad to hear that, thanks for feedback!
Bro you are a life saver my demo is ready for google io
Great to hear! You can share a link here 🙌
Thanks guy. This video really helped me.
You're welcome! 😊
Really good video, thanks man!
Glad you liked it!
Very helpfull ! Thank you man..
Glad that it worked for you 👍
Thanks for the tutorial! I’m currently migrating my current live portfolio (already with firebase) from basic html/css/js to nextjs/tailwind.
I have a question: so I just need to select the "Use an existing project" option (which is my live portfolio) to deploy the new nextjs portfolio? And would the files of my old portfolio be automatically fully replaced?
If you already have a project and choose it when deploying then yes, files will be replaced.
thank you for this tutorial, saved me a lot of time!
You are welcome, make sure to check out my website to find more free methods of deploying Next.js
Thanks for this tutorial - got my site up and running. I'd be interested in a more complex tutorial with subdomains :)
Thanks for the feedback. You can deploy to a subdomain the same way as your main domain 😉
@@tsykin how 😢 with Next JS 13
@@davidlintin i think you can just deploy your app following my guide and then assign this app a domain in firebase.
great tutorial 🙏 u got a new sub 👍
Thanks a lot for the sub 👍
Works. Thanks!
thanks for tutorial❤❤
You're welcome 😊
Thanks for the video! :)
You are welcome! 😊
Great tutorial,
Thanks
Very helpful!...
You are very welcome 😊
Super helpful 👍👍👍! Thanks a lot.
Glad it was helpful!
super useful
Glad it helped 🙃
great tutorial 👍👍👍
Thanks, glad I could help 😊
thanks!
Happy to help 😊
I have a next 14 app running nicely but when i deploy it on firebase the videos are not uploaded when i check the source of the website.
Make sure that files are included in the project. Also, are images being uploaded normally for you?
Hello guys, I have the same problem. I discovered that occurs because the default req for next server contains _next in the url, and firebase doesn't support this. There's some tutorials on the web teaching how to configure, but just older versions of Next. Can you guys solved the problem?@@tsykin
Thanks 🎉
You are welcome 😊
Hopefully that helped you deploy your app to Firebase Hosting
Great tutorial! thanks. Just one question, do you know if all the features from Next.js, like server side components/functions and etc are available when using Firebase hosting? I did read somewhere that a Node.js server is needed for that, but I don't have a clue of how Firebase hosting works.
Thanks for feedback. I am yet to test deployment of an app with advanced functionality, so I might come back with information on that. For now it's up to you to use my tutorial to test out those features 😊
If you don't have a pay-as-you-go plan on firebase, this won't work. You're better off deploying with vercel or netlify. It is also much faster
Of course using hosting platform is faster and easier. But it's also pricy and sometimes lacks ability to go inside the machine that hosts your app. That's why I showed how to host you Next.js app for free on a VM 😊
And yes, you might need to add credit card details to Google Cloud when setting this up, but you won't be charged anything if done correctly.
@@tsykin Ohkay thanks for the info 👍
You forgot to mention that Firebase require you to have paid account for this - Pay as You Go
Thanks for the feedback 😊
Actually, I did mention it in my post (text version of this tutorial). Check the first link in the description
@tsykin sorry, my fault 😔
@@VASILASIS it's OK. Did it work for you after all?
Yes, but still requires HTTPS when call backend :-( The same as Vercel. So - no difference between Vercel deploy and Firebase
@@tsykin
Is work for SSG?
Yes, it should work for Static Site Generation.
Normal pages are loading fine, But when I deploy nextjs project with dynamic pages I'm getting error like this.
Building a Cloud Function to run this application. This is needed due to:
• non-static component /todos/[id]/page
Unable to bundle next.config.js for use in Cloud Functions, proceeding with deploy but problems may be enountered.
The command line is too long.
How can solve this issue?
Thanks for reporting this. To be honest I am a beginner developer and I have not encountered this issue.
Hopefully someone more experienced will reply to your comment.
Put "use client" all of pages if you don't use Server Side Rendering
@@heynerhumanez4406 Thank you very much
wow i really like the zeal just continue it will pay off later💪💪🚀🚀🔥🔥
Thanks ! So useful
Glad it helped 😊