NestJS Crash Course - Build a Complete Backend API

แชร์
ฝัง
  • เผยแพร่เมื่อ 10 พ.ย. 2024

ความคิดเห็น • 45

  • @armaganvideos
    @armaganvideos 2 ปีที่แล้ว +30

    You should give a hint that the left-panned audio in the intro will resolve later on or people might jump ship :D

    • @JimKim-0
      @JimKim-0 5 หลายเดือนก่อน

      bruh, you saved me lol

  • @ugochukwuavoaja8924
    @ugochukwuavoaja8924 2 ปีที่แล้ว +1

    Thank you Laith for the great content once again. I had to buy the Udemy course so I can the advanced parts.

  • @syedalishahbukhari8638
    @syedalishahbukhari8638 2 ปีที่แล้ว +2

    Awesome 👍. Please make a course on TypeOrm

  • @afamsval
    @afamsval 2 ปีที่แล้ว +1

    You are the best Sir. Thank you for always using typescript in most of your projects

  • @yassineaker
    @yassineaker 2 ปีที่แล้ว +1

    I'm looking forward for the next big project. Could you let us know when it will be published?

  • @leanprogrammer
    @leanprogrammer 2 ปีที่แล้ว

    Great stuff. The amount of content you provide on here is ridiculous! How are you so productive???

  • @saadowain3511
    @saadowain3511 2 ปีที่แล้ว

    Thanks alot. Will buy the udemy course.

  • @mahdisalmanizadegan5595
    @mahdisalmanizadegan5595 2 ปีที่แล้ว +1

    great course

  • @GabrielGasp
    @GabrielGasp ปีที่แล้ว +1

    Hey Laith, just letting you know that there is a TH-cam channel named Voxmind with your udemy NestJS course (and a bunch of courses from other people). You might wanna do something about that.

    • @laithacademy
      @laithacademy  ปีที่แล้ว +1

      Thanks friend, I’ll try to take care of it

  • @abdullahh.abdulazim228
    @abdullahh.abdulazim228 2 ปีที่แล้ว +6

    Good stuff Laith, wanna suggest that you consider adding a mongoDB/nest mongoose with GraphQL as an additional section in your Udemy course, that would be great!

  • @boristheblad
    @boristheblad ปีที่แล้ว

    Very solid.

  • @rakshiths.n9680
    @rakshiths.n9680 2 ปีที่แล้ว +1

    Can we know what are the topics and technologies your are working on ...

  • @rakibullahsazib1268
    @rakibullahsazib1268 2 ปีที่แล้ว

    Thanks Laith. But I don't see any discount on udemy.

  • @dumpst3r68
    @dumpst3r68 2 ปีที่แล้ว +2

    thanks for the great video, Laith.
    Out of curiosity, is there a particular reason you filter AND find a report? Find will return the first report for which the id === the id passed in, so wouldn't it make sense to use either filter (filter by id) or find (by id)? Seems almost redundant.
    The only use case I can see for this is when you initially set up your data.ts, if you have two ids that are the same.
    Thanks, and again, great job. I love learning from your content.
    Example:
    ```
    [ { 'id': 1, 'value': 'yes'}, {'id': 2, 'value': 'no'}, { 'id': 3, 'value': 'yes'} ].filter(report => report['value'] === 'yes').find(report => report.id === 1) will return { 'id': 1, 'value': 'yes'}
    [{ 'id': 1, 'value': 'yes'}, {'id': 2, 'value': 'no'}].find(report => report.id === 1) will also return { 'id': 1, 'value': 'yes'} (as will just [...].filter(report => report.id === 1) )
    ```

    • @piotrjan2927
      @piotrjan2927 2 ปีที่แล้ว

      As far as I can see, we filter by report type, and then find by item id.
      We could just use find(r => r.type === type && r.id === id), but it would return exactly the same result.

    • @Slayre77
      @Slayre77 2 ปีที่แล้ว +1

      I am curious about this as well. Assuming all IDs are unique, why do we have to filter for the type before finding an individual instance of report?

    • @fleckenfurz77
      @fleckenfurz77 2 ปีที่แล้ว

      @@Slayre77 I am wondering about this longwinded approach as well...
      I think:
      const report = data.report.find(r => r.id === id)
      report.amount = body.amount
      report.source = body.source
      return report
      ..does exactly the same

  • @improvingwithfun
    @improvingwithfun ปีที่แล้ว

    explaining things like what is request or how REST works in NodeJS framework course is a bit more than harsh :D

  • @drewpetricc
    @drewpetricc 2 ปีที่แล้ว +1

    Love this video, bought the course on udemy too. Anyone know how are he is formatting lines like @2:36:35 ?? I know on Mac it's shift+option+F by default to 'format' but is that all that's happening? Thank you for all your great teaching Laith!

    • @mrsrv7
      @mrsrv7 2 ปีที่แล้ว

      He might have the format on save turned on. If you see once the file is saved, the code is formatted immediately.

  • @nnaemekaish007
    @nnaemekaish007 2 ปีที่แล้ว

    Great, now I can apply to Prod***

  • @codernerd7076
    @codernerd7076 2 ปีที่แล้ว +1

    If only it had one 3rd project with Graphql and Auth to follow up the other course, also does the final project use secure cookies?

  • @moylababa8196
    @moylababa8196 2 ปีที่แล้ว +3

    Please make a microservice tutorial using Node.js

    • @NathanielBabalola
      @NathanielBabalola 2 ปีที่แล้ว +1

      Tbh it's very important, tutorials on this is very rare

  • @wahebbenzaid543
    @wahebbenzaid543 2 ปีที่แล้ว

    Nothing to say ! this is a great tutorial, I was waiting for it. By the way, what do you recommand for a nodejs beginner, express or nest ?

    • @zedshockblade7157
      @zedshockblade7157 2 ปีที่แล้ว +1

      nest is built on top of express. so express first.

    • @centereddev
      @centereddev 2 ปีที่แล้ว +1

      I would probably say Express too since it's much simpler, but there's something to be said for learning a framework with strong conventions like Nest early on. I Iearned Ruby on Rails early on and it helped me recognize conventions in other frameworks.

    • @justhooman4682
      @justhooman4682 2 ปีที่แล้ว +2

      if you're not looking out for a job, expressjs will do for everything. otherwise, learn expressjs with pretty much everything you would want to do in nestjs if you're new to backend, and then migrate to nestjs. this way you won't have to tackle everything at once.

  • @geelemo
    @geelemo 2 ปีที่แล้ว

    hello, I'm having an issue where when I throw new HttpException or any type of exception my app stops running and is terminated. Also the response code remains 201. Any help?

  • @dreamystudents2666
    @dreamystudents2666 ปีที่แล้ว

    Hy Mate, your videos are really amazing , please also make a video with this (Nest JS, TypeORM, GraphQL and PostgresQL) stack, thank you :)

  • @ol1175
    @ol1175 2 ปีที่แล้ว

    Thanks , good one!

  • @mahendranath2504
    @mahendranath2504 2 ปีที่แล้ว

    Thank you so much ❤️👍🏼🎉⭐🙏

  • @abessesmahi4888
    @abessesmahi4888 2 ปีที่แล้ว

    Awesome 👌

  • @edwardkeselman5118
    @edwardkeselman5118 2 ปีที่แล้ว

    Is there a reason not to use Expose decorator with the name createdAt over created_at property? I tried it and it worked, why do I need to expose a method?

  • @manoj-k
    @manoj-k 2 ปีที่แล้ว

    🔥🔥🔥

  • @webpro1608
    @webpro1608 2 ปีที่แล้ว

    Nice👌

  • @eli007s
    @eli007s 2 ปีที่แล้ว

    meh coupon no longer works =/

  • @ryanrahman26
    @ryanrahman26 2 ปีที่แล้ว

    Thank you very much..... i can't speak

  • @MaksymMinenko
    @MaksymMinenko 2 ปีที่แล้ว

    You should have used Prisma.

  • @H_I_R_B_O
    @H_I_R_B_O 2 ปีที่แล้ว

    BRO.....your first section has no sound man

  • @gilbertocolten1789
    @gilbertocolten1789 2 ปีที่แล้ว

    This is the part of my day I always enjoy!! The secret to success = P R O M O S M!!!