I can see you becoming "that nestjs guy". Very easy and straightforward explanation. Thank you.
@mariusespejo2 жыл бұрын
Thanks! I don’t really plan to be though 😄 there’s so much more to web dev that I’d like to cover but I’m building up to it
@eddyv524 Жыл бұрын
Sir, you are a really good teacher. Very calm and crystal clear.
@mariusespejo Жыл бұрын
Thank you!
@johnparungao1354 Жыл бұрын
i love binge watching your tutorials , feels like im working with a senior during my free time .
@saveliy.d_13 Жыл бұрын
Best explanation of how to make a simple app using websockets. Thank you
@StrayKev2 жыл бұрын
I found your channel about a week ago, and I am really enjoying the content you are making. Keep up the good work!
@mariusespejo2 жыл бұрын
Glad to hear that! Thanks for stopping by to comment!
@wxchen-v8p26 күн бұрын
im very happy to find you,my nestjs savior!!!!
@flavioextreme12 жыл бұрын
You are a saint my friend, if I still had hair I would have ripped it all out without understanding websocket
@thecastiel692 жыл бұрын
do you recommand dt 770/pro for watching movies?
@mariusespejo2 жыл бұрын
I haven’t tried movies although for music I think it sounds amazing. It’s meant to be a studio monitor so it lets me hear all the details. I’m not an audio expert at all but that does mean it’s meant to be somewhat “neutral”, and I’m not sure what’s ideal for movies. For my use case if it’s not obvious I use it to monitor my mic to make sure it’s not recording things it shouldn’t, and to generally hear its quality in realtime as well as in post production
@minhoannguyen85432 жыл бұрын
thanks for your tutorial, please realease more content Nestjs like this
@mariusespejo2 жыл бұрын
😄🙌
@wiratleenavonganan64532 жыл бұрын
Many thanks for NestJS tutorial. Very handy!! I really enjoy learning.
@AliAliOxenFree Жыл бұрын
This is amazing. Thank you for creating this tutorial marius, always a treat to watch your content
@aldaineclarke7552 жыл бұрын
I am really happy I found this vid...I'm planning to use WebSocket in nestjs. Thanks for the vid..
@mariusespejo2 жыл бұрын
Great! Good luck on your project!
@aldaineclarke7552 жыл бұрын
@@mariusespejo thank you💪🏿
@agiraldodev Жыл бұрын
Your desktop wallpaper is great!..
@damianlluch11 ай бұрын
Excellent video. Can you share the repository of the project you created in the video?
@sagar79292 жыл бұрын
Also make a complete tutorial on soft delete with nestjs and prisma🙏🏽 Thank you so much for this tutorial🙏🏽🙏🏽
@ashishkumari-yg4gn Жыл бұрын
soft delete can implemented just by using deletedAt as null and adding this filter in each query
@metatronicx2 жыл бұрын
Thank you very much for this content 🤗🤗. With this out now, I think you have covered a lot of stuff in nestjs. Be blessed
@mariusespejo2 жыл бұрын
Thank you 🙂
@developer_anything6 ай бұрын
thanks from Indonesia, its awesome💯
@mariusespejo6 ай бұрын
Hello! 👋
@lapaklapakap Жыл бұрын
where Source code :(
@hermes.j.pappas Жыл бұрын
Great tutorial! Thanks so much 🙏
@LucasAlexK Жыл бұрын
Have you thought about having the source code for each video somewhere? Would be super useful 🙌
@Gokuroro Жыл бұрын
In 30:57, won't the setTimeout actually kind of bombard the clients with multiple "isTyping = false"? For each time we're calling the "isTyping = true" event we're creating a new setTimeout and actually de-referencing it afterwards, without killing the original first. (maybe this is covered later in the video, but I wanted to mention it before I forgot, sorry if it is already covered)
@mariusespejo Жыл бұрын
Sorry been a while since I wrote the code but I think you’re right, probably ideal to clearTimeout, I think I intended to do that that’s why we have the timeout variable defined. Basically we’re just trying to debounce there. Good eye!
@sanwalfarooque274710 ай бұрын
@@mariusespejo I was going to comment the same thing.
@shiengng5779 Жыл бұрын
Hope can get video for further implementation of this websocket in Nestjs, like updated edit features or multiple room
@mariusespejo Жыл бұрын
Yeah I think that would be fun to build! I’ll see if I can plan for that, thanks for the suggestion
@suryohastomo94392 жыл бұрын
thanks, the tutorial so helpfull. i hope can add an other project like this with reactjs
@higol5596 Жыл бұрын
Thanks a lot. Websocket can reduce the network traffic if sending only new messages as broadcast. I am wondering if the app can make high avaiable (multi k8s pods)
@nikhilgoyal0076 күн бұрын
thank you! is their a way to customize generate resource - for eg. to generate a prisma schema file instead of the entity file ?
@mariusespejo6 күн бұрын
Hmm I have not seen a way to customize
@insomnia6961 Жыл бұрын
Great Video as always. Could you make a follow up on this that goes a little more in depth? would be really nice (chatrooms and stuff and maybe with local strategy auth). Greetings!
@mariusespejo Жыл бұрын
Yeah that could be a fun tutorial, will think about it!
@mandlankosi2160 Жыл бұрын
MARIUS ISTHE LIONEL MESSI OF NEST JS. thanks for this bro. awesome
@rafaelgoncalves15262 жыл бұрын
Nice content, dude!
@muhammadrizotursunboev68542 жыл бұрын
thank this lesson is really good
@mariusespejo2 жыл бұрын
Glad you think so, thanks!!
@MartinPerez-mi1ty2 жыл бұрын
Nice video, what vs theme are you using?
@mariusespejo2 жыл бұрын
Monokai pro on this one I think!
@AhmedHassan-sd1ty2 ай бұрын
quality content.
@MegaMurimi Жыл бұрын
Great video! Do you have a repo of this?
@golu8045 Жыл бұрын
I want to create a project like whatsapp, where users choose the user which one I want to talk, and user click on them and send an message, and only that person get notified and receive the message I want to add this type of functionality in my nestjs app how can I implement this? please help
@mariusespejo Жыл бұрын
Take a look at socket.io, I believe it has built-in support for rooms
@golu8045 Жыл бұрын
@@mariusespejo can you please make a video in this topic?
@amaranthus7737 Жыл бұрын
You're great, thanks alot
@mrbelkabachi2 жыл бұрын
When you are working on REST API you can document your controllers using Swagger but what alternatives do we have while workig on sockets?
@mariusespejo2 жыл бұрын
There’s a thing called swaggger-socket but that’s only if you were attempting to do REST over websockets, which is probably uncommon. Other than that I’m not sure there’s any common standard for how to structure websockets so there likely isn’t much swagger-like solutions. You could always make your own custom documentation though
@mrbelkabachi2 жыл бұрын
@@mariusespejo thanks
@NursultanBegaliev3 ай бұрын
Thank you! 👍
@mariusespejo3 ай бұрын
You’re welcome!
@BioInASec Жыл бұрын
I wonder how you are able to explain such things in a very simple way, Keep this up and maybe consider telling us how you approach learning these new things! Thanks Anyways
@mariusespejo Жыл бұрын
Thank you, that could be a good video topic for the new year (how to approach learning things)! Will definitely consider it
@BioInASec Жыл бұрын
@@mariusespejo Dying to watch it
@David-rz4vc2 жыл бұрын
Can you do a video on nest with casl but dynamic permission assign to roles stored in the database?
@mariusespejo2 жыл бұрын
I’ll consider it, I don’t think there’s really much to it though, just store the rules as JSON and manage it. Casl can initialize an ability from json
@zackboudeffa1826 Жыл бұрын
great work v😍, but i think it's way better if u add the source code.
@104antony10 ай бұрын
Hello, great video. Can you share the Github link , so I have to study it more easily? Thanks!
@mariusespejo10 ай бұрын
Hey! I’m sorry but the code isn’t on github
@104antony10 ай бұрын
@@mariusespejo Okay, thank you anyway :)
@user-tt6nc6mo7k2 жыл бұрын
I'm torn between sending the real-time data in the payload and just publishing a new "resource" created event and having the clients that are subscribed to that event re-fetch the data for that resource. On one hand, you save having your clients send multiple requests for the resource by including the data in the payload. On the other hand, by forcing them to re-fetch the data, you get to have one source of truth. Thoughts?
@mariusespejo2 жыл бұрын
I’m sure there are more details to your use case but my gut reaction is that: if you’re already using websocket, meaning you have a persistent connection, why wouldn’t you just send the data directly? You still have one source of truth which is the server who now says “hey all you clients this is now the current data!” And clients could react and update immediately. However your other idea of simply publishing a trigger, it still means that each client still needs to spend additional time to fetch data which sounds like could have been available to them at the same time they got the trigger. However, there is nothing inherently wrong with that approach. If it’s because you’re just trying to reuse APIs, that makes sense to me
@user-tt6nc6mo7k2 жыл бұрын
@@mariusespejo Hmm, that is a very good point. I just have to make sure that all data transformation occurs upfront within the service's method before returning it. Then it would be as you said with the server being the source of truth. Thanks.
@amir84882 жыл бұрын
thnks for your videos, bro
@mariusespejo2 жыл бұрын
Yeah man, glad you like it!
@franciscoroca94448 ай бұрын
ey mate, do you have the code? I am trying run it but connection refused all the time.
@mariusespejo8 ай бұрын
Hey sorry not on github at the moment, I recommend taking a look at the official docs for the most up to date guidance
@franciscoroca94448 ай бұрын
My issue was related with my M2 chip and my node version. Is already working fine. Thank you for your answer.@@mariusespejo
@vannguyenthai22212 жыл бұрын
My vue demand v-for key, can i know what it is
@vannguyenthai22212 жыл бұрын
if anyone get the error like me, give it a key like this should work
@antnzr6562 жыл бұрын
Hello. How do you store connected users on the server in the real applications?
@mariusespejo2 жыл бұрын
The underlying websocket library you use like socket.io usually will take care of keeping track of which clients are connected. You just need to build a way for your server to identify who the user is on that client, e.g. basically auth. Put those two together and you’ve got your list of connected users.
@Alexlinnk Жыл бұрын
very nice
@eddyv524 Жыл бұрын
Can gateways be protected by using guards?
@mariusespejo Жыл бұрын
To some degree yes, here’s an example: stackoverflow.com/questions/58670553/nestjs-gateway-websocket-how-to-send-jwt-access-token-through-socket-emit However I don’t think you can add a guard to the entire gateway as a whole, and notice in github open ticket for handleConnection, can’t put a guard on it: github.com/nestjs/nest/issues/882
@digitalwerse2 жыл бұрын
thanks so much, and how can we authorize connected users?
@mariusespejo2 жыл бұрын
I have some videos on auth. The fundamentals are all the same, you need a way to identify the user (e.g. perhaps upon connection require a login event, or do login via REST prior to allowing a connection). Once you can identify which user is dispatching an event, then it’s up to you how to do authorization, you can pull the user record and check they have permissions etc. Generally with nest you can utilize guards to do those checks. Few videos about that in the channel
@JohnSmith-le3xv2 жыл бұрын
Tell please, what is that font u're using?
@mariusespejo2 жыл бұрын
I believe I’m using cascadia code at the moment, I’m not sure haven’t changed it in a while
@trephy2999 Жыл бұрын
Would be cool to paste less code in. Sometimes I was a bit lost on where I should write what and where your code came from. Otherwise great Tutorial, keep at it!
@mariusespejo Жыл бұрын
Thanks for feedback. Definitely still trying to find a good balance for things such as pacing and writing vs pasting code
@johnsonwu40752 жыл бұрын
can you share those code ?
@mariusespejo2 жыл бұрын
Sorry it’s just in the video for now, you’ll find it’s actually not a lot of code to write
@Mr_Stork2 жыл бұрын
Nice tutorial, unfortunately after refresh page names doesn't appear in my messages.
@mariusespejo2 жыл бұрын
You can dispatch the current list of messages to a client when they connect, or you can use a separate API call to fetch it initially. Various ways to go about it
@David-rz4vc2 жыл бұрын
Yess!
@abdella29472 жыл бұрын
Hey @Marius thanks a lot for all your Nestjs content I really learned a lot from your channel. I have a request if you don't mind it would be helpful for me and a lot of ppl in the Nests community. I been trying to find a Nestjs React WebRTC video tutorial and surprisingly could find a single one online or youtube! If you could please create one that will be amazing!
@mariusespejo2 жыл бұрын
Thanks for the suggestion, will keep it in mind!
@neonsegaming31142 жыл бұрын
Can we use graphql subscription?
@mariusespejo2 жыл бұрын
You can! Graphql subscriptions use websockets under the hood. So it’s just a different interface basically but same idea. I have an example of that in my teamseas video if you’re interested
@neonsegaming31142 жыл бұрын
@@mariusespejo yes please i am migrating to fully graphql with graphql-ws
@mariusespejo2 жыл бұрын
It’s in the channel!
@TheWalrus_452 жыл бұрын
@@mariusespejo Is this the same as Server-Sent Events?
@mariusespejo2 жыл бұрын
Paul, sorry misunderstood the question. No it’s not the same as server-sent, which is not bidirectional like websockets are
@sagar79292 жыл бұрын
Please also makje a tutoril on the topic of Server sent event on nestjs using prisma
@mariusespejo2 жыл бұрын
Using websockets is already one of the ways to directly push events from the server, what else are you looking for exactly?
@sagar79292 жыл бұрын
@@mariusespejo to learn more as to understand the alternative way too.. I just heard sse is also good fot push event and compare to web socket, sse is good to go - i don't know what is it so I am here to know! If possible do make a tutorial one🙏🏽
@mariusespejo2 жыл бұрын
Ah! I actually didn’t even know that was a thing, today I learn from you, thanks! I’ll look into it and maybe form opinions about it first. But at quick glance, it looks like it’s not bidirectional so the use case is limited to communication only coming from server. Also there is a hard limit of 6 connections per browser, unless it’s on HTTP/2 … that sounds pretty limiting. I could see this being useful for push notifications though!
@امیرحسینفکری-ل6د2 ай бұрын
tnx bro
@christianangelomsulit37592 жыл бұрын
Hi can you do socket authorization next? :)
@mariusespejo2 жыл бұрын
I have a few videos on authorization already, it’s pretty much the same principles. E.g. see the CASL videos that I’ve made
@art76532 жыл бұрын
Please, leave github link on project here
@rasulrukh29072 жыл бұрын
good job, but every video tutorial about programming must have a link to the source code IMHO)
@mariusespejo2 жыл бұрын
Sure thanks for feedback, I’ll think about it. My content is already designed to be something you can follow along with from start to finish though. There are a lot of people that simply want the code and not to watch and you just won’t get the same value out of the content that way in my opinion.
@TalebBahan Жыл бұрын
great men thinks
@Komissar666 Жыл бұрын
add repo pls
@leonelpaulus10952 жыл бұрын
thanks for your excellent tutorial, but I'm kind of tired of people explaining the same real time chat application example. I cannot find a way to connect to an external webSocket from an exchange for example to retrieve book orders, and there is not a single tutorial on consuming an already existing webSocket. So frustrating.
@mariusespejo2 жыл бұрын
It’s important to look past the “it’s just another chat app” and actually learn and understand the underlying fundamentals required to engineer a more specific problem, e.g. if you’re putting together your own real-time feature. Your use case however is about integration with a 3rd party. Any external api generally should include usage docs, you should rely on that not tutorials. If it doesn’t have docs… reach out to the devs
@rcharles2683 ай бұрын
Source code
@zawriter47832 жыл бұрын
Hey Marious, Is everything okay? You have been off for so long. :)
@mariusespejo2 жыл бұрын
Thanks for checking in, everything is good! I am working on a new video, just had a lot on my plate this past month
@haralc Жыл бұрын
Why 1/4 of the screen is your face? We all came here for the code ...
@mariusespejo Жыл бұрын
but you’re the only one who has complained so far lol have a great day
@fatinnayhan44632 ай бұрын
bang agamanya apa
@HarshChauhan-gr5yu6 ай бұрын
Seriously worst possible tutorial you are just creating the entire application without any checkpoints
@mariusespejo6 ай бұрын
There are timestamps in the description…? what checkpoints are you looking for?
@HarshChauhan-gr5yu5 ай бұрын
@@mariusespejo We need to check in between how server is working. Postman testing in between so that people can code along. As of now we I say I want to code along with you I would just get to know my codes works at the end of the video