3:02 The "moduleResolution: node" was deprecated, so instead using "node" it's helpful use "NodeNext" or leave without definition. Awesome tutorial, you helped me a lot!
I just completed this video, I can say confidently that it's an outstanding video, it has skyrocketed my knowledge in node, and my ability to create REST API, structure my directories correctly, and lots more. Thank you so much Antonio🙏
This is an outstanding video. Most of my work has been with Nestjs and postgres, but this gave me a clear perspective on a different approach to handle the same REST endpoints. earned yourself a loyal sub!
As a front end developer, I finally finish This REST API tutorial in a week. Great Great! Thank you very much! I will conquer all your courses One at a time! Really having fun coding with you Antonio!
@@codewithantonio hello Antonio! BIG THANKS for thios video, but i have a question. why are you using http here, when u can just put app.listen and server is going to work? im not blaming, jsut cant get it
I want to show my appreciation for your useful video,I highly recommend to every person who is looking for do complete CRUD with Node,this video is so handy and you can get whatever you need for your REST API.
Hi Antonio. I found your channel recently and completed coding the REST API. I learnt alot and amused with the way you explain & code all the stuff. I hadn't found a channel like yours before. However It's all super clean❤ You deserve more followers than you have rn. Keep up the great work🤍🥂 Lots of love from Sri Lanka🇱🇰
Wow~~ This is the course I was looking for. I wanted to see a lecture made with node typescript thank you. I should have seen this lecture sooner. I used google translator.
For the next videos, Can you please Add mongodb all relationships such as one to one, one to many and many to many. It's a topic in which I have lot interest. Thanks
@@RebaiMoez There can be relations between collections in document DBs. While it is advisable to denormalize, there are certainly scenarios where you would query a collection by FK.
Good tutorial but it might be more helpful to also mention what certain parts of the code are doing and why they're there. At one point, a line is added that is "extremely important" or else the code will not work. It would be nice to get some explanation about why that is exactly.
Pretty interesting stuff. I was looking for Graph QL but landed on this video and couldn't quit) A great video for baking a boilerplate for future projects. Thanks.
I've had having some trouble getting my code to run properly. My main two issues were with user login and checking if an email already exists in the database. My solution was to import the 'User Model' into my controller file and use the findOne method. That little fix did the trick. I'm a junior software developer, so don't get mad at me, seniors software enginnering! lol!
Personally, I would not suggest it for beginners; there is little to no explanation and it might be quite daunting for those of you who are just getting started.
Great video! i was struggling with back-end and this really cleared my mind. What would you recommend when it comes to testing? A video focused on TDD with typescript would be great :)
At around minute 32 I get errors: user.authentication.salt, .password and .sessionToken are "possibly undefined". I checked my users.ts file and it seems to be exactly the same as yours. What do I have to do in order to make this error disappear?
One way woudl be to add an explicit guard check like so: if (!user || !user.authentication || !user.authentication.salt) { return res.sendStatus(400); }
Hi there ! I would like to address a bug which I encountered while following this tutorial. If anyone is getting the following error in their app: Error: Cannot find module 'helpers' Require stack:.... Then you need to fix your imports from this - import { authentication, random } from "helpers"; to this import { authentication, random } from "../helpers"; For these '../' I spend a lot of time debugging. Thanks for the tutorial Antonio.
sir antonio can you make a masterclass for this, like "next-auth" like having a logic to implementing "email verification, password reset, otp, oauth provider, role base"
Nice tutorial for this in typescript, for unknown reason the post is deleted, so i write again, haven't go throught it but just notice you still use bodyparser, since 4.0 express have already integrated it, so you don't need anymore and you can replace the middleware with express.json() :)
i watch your videos they well put together with advanced development practice but can you do a more in depth explanation tutorial for some us are not following at some instance
you cannot deploy server side applications like this API to netlify, unless you deploy it as serverless function. although you can easily deploy it to render. but render doesn't allow your server to run all the time it shuts down after 15s from last call, and it takes too long to restart and send back response when you call it again after 15 min. better alternative is vercel but you have to configure some files to be able to deploy an api to it.
The thing about storing salts is a very old concept that was discarded, it discouraged, unless something has changed and i don't know, you just don't need to save it.
Thank you for pointing this out! I will take a look at my decisions in this video and see how it can be improved, I actually did not use salt as you said in my Netflix and Twitter tutorial, so you're probably right :)
Hello Antonio and thank you for the great content. I have watched until 33:41 (end of authentication) and I have some questions. 1) Isn't it better to use bcrypt instead of crypto for hashed passwords? 2) Isn't it better to use a .env file to save your passwords instead of using them directly in code? 3) Isn't it safer to use jwt instead of this session token? 4) Shouldn't the cookie and the token have expiration dates? 5) Like this is the authentication safe enough to use against common hacking attacks?
Anyone else having problems with postman? I followed everything to the t, but when it comes to postman for the first time (27:45) to register a new user, I am getting a "404 Bad Request". In Postman I am choosing "POST" with the exact same route as in the video. What am I missing? 🤔
I found the error for me to be with the controllers/authentication.ts file. The if statement to check the parameters was checking if they were true instead of false and returning an error.
Hi, Antonio! thx for a nice tutor! As a cpp backend dev (no experience in web) I'm wondering, why not use OpenApi notation for API declaration and sever creation?
