While this is nice and all, isn't it now no different than any other OOP-language code? Now I'm not saying javascript is good for the sake of being different, but why go all this length with the setup of tens of different libraries, when you could've arguably done it faster with the same result in .NET?
Cubicle code monkey & into history
I like design & UX, though I'm far from where I want to be skill wise; improving little by little every day.
Lax writer; need to blog more often
Question: why did you use NestJS with NextJS? Isn't this all possible leaving out NestJS since NextJS has routing? I know NestJS, but I'm very new to NextJS.
Next.js is a react framework that provides SSR(Server Side Rendering) easily.
So if you want to use react with better SEO, Next.js is one of the best choices.
Nest is just a server framework, so it doesn't care about client side.
Generally way, web services have two repositories: server repo and client one.
But I think it's complex enough to learn or test simple web stack :)
Feel free to open issues if you have any troubles :)
By the way, I'm currently working on react-ssr, which is an alternative to NEXT.js. (I think)
This renders React as a view template engine of Express like this:
// server.jsconstposts=[{id:1,body:'This is a first post.'},{id:2,body:'This is a second post.'},{id:3,body:'This is a last post.'},];app.get('/',(req,res)=>{res.render('index',{posts});});
thanx , this is a very good work. I dont know if you have the time to help me, I can't run your code on dev. I thing the problem is in next.config.js file
We're a place where coders share, stay up-to-date and grow their careers.
While this is nice and all, isn't it now no different than any other OOP-language code? Now I'm not saying javascript is good for the sake of being different, but why go all this length with the setup of tens of different libraries, when you could've arguably done it faster with the same result in .NET?
Because not everyone wants to use .Net.
.NET doesn't handle JSON as efficiently as Node.js. However, this tutorial uses postgres instead of mongo, so good point.
Awesome project, I was just about to start an auth project just like this with the same stack!
Thank you sooo much!
I hope you enjoy it :)
NestjS and NEXT.js are so awesome, I believe.
do you have any problema by running on dev?
Good post, great work!
Thank you very much!
I'll implement social login like GitHub, soon :)
Question: why did you use NestJS with NextJS? Isn't this all possible leaving out NestJS since NextJS has routing? I know NestJS, but I'm very new to NextJS.
Next.js is a react framework that provides SSR(Server Side Rendering) easily.
So if you want to use react with better SEO, Next.js is one of the best choices.
Nest is just a server framework, so it doesn't care about client side.
Generally way, web services have two repositories: server repo and client one.
But I think it's complex enough to learn or test simple web stack :)
Cool post,exactly what I was looking for, for studies.
Thanks Igor!
Feel free to open issues if you have any troubles :)
By the way, I'm currently working on react-ssr, which is an alternative to NEXT.js. (I think)
This renders React as a view template engine of Express like this:
If you like, please try it :)
Thank you in advance!
Yoshihide
thanx , this is a very good work. I dont know if you have the time to help me, I can't run your code on dev. I thing the problem is in next.config.js file