Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "nestjs"
-
Could not fucking sleep at all.
Spent the entire night in a combination of:
Weight lifting
Playing with NestJS(its fucking beautiful)
Watching seven deadly sins on Netflix(current fav anime)
And i am still not tired. Even then I am not in the mood for going to work.
Not sure if I want to risk it and drive there since I know I will be crashing at around noon.
I hate it when this happens.
During the week I would do crazy shit to try and get me to fall asleep.
I would wake up early. Work out, go to work, get back from work, kill myself at the gym and nope.
Still wide fucking awake.
To make it better, my stomach begins to act up and fucking kill me the more I don't sleep for some reason(although it could be related to me piercing my stomach years ago)
I really dislike being human. Such fragile bodies.
But yeah, NestJS is frickin amazing. Typescript is sexy as all hell with it. Just what i was looking for in terms of out of the box architecture for JS apps5 -
"I created the Best NodeJS framework of all time. Because other frameworks are so stupid.
Check out my work https://github.com/mayajs/maya
All other frameworks are dumb. mine is the best.
Support mine instead. NestJS sucks.
Follow me on twitter: https://twitter.com/IgnacioMack
"
Fuck you7 -
So I am working on a cloud app, Angular on the frontend and NestJS with heavy AWS dependency at the backend. I took my time to learn the stack and I have a couple of years of experience with each piece involved.
Since I am a Level 1 developer, management thought (and I felt same way) it would be nice for me to work with a couple of Level 3 devs.
Well, they hired Level 3 devs:
- a senior Java developer who never touched AWS, any kind of frontend or Typescript
- a senior c++ dev with the same “never touched” as above
And guess what? I have to train them both in Angular, Typescript etc. Kinda defeats the whole purpose of L3, “they will help you to deliver stuff fast”, and adds load on me (I am already a shared resource on 3 teams).
Oh, and yeah, management already promised to release the app by the end of the year and so far I am the only capable and functional developer on the team who has to deliver everything.
I had so much hope for new hiring cycle lol10 -
My MEAN stack study is about 75% now but then I keep on getting some new cool things like integration of NestJS and Redux in the MEAN stack.
MEAN Stack - a very big steep learning curve but I like it.1 -
A lot of this might be an assumption based on not enough research on both NestJS and TypeScript, so if something here is not well put or incorrect then please feel free to provide the necessary info to correct me since I care far more about getting dat booty than I do being right on the internet :D
Sooo, a year or so ago I got a hold on the Nest JS framework. A TypeScript based stack used to build microservices for node. Sounded good enough in terms of structure, it is based on the same format that Angular uses, so if you use Angular then the module system that the application has will make sense.
I attempted (last night) to play with the framework (which I normally don't since I am not that much of a big fan of frameworks and prefer a library based approach) and found a couple of things that weird me out about their selling points, mainly, how it deals with inversion of control.
My issue: This is dependency injection for people that don't really understand the concept of dependency injection. SOLID principles seem to be thrown out of the window completely due to how coupled with one another items are. Literally, you cannot change one dependency coming from one portion to the other(i.e a service into a controller) without changing all references to it, so if you were using a service specification for a particular database, and change the database, you would have to manually edit that very same service, or define another one....AND change the hardwire of the code from the providers section all the way into the controllers that use it....this was a short example, but you get the gist. This is more of a service locator type of deal than well....actual dependency injection. Oh, and the documentation uses classes rather than interfaces WHICH is where I started noticing that the whole intention of dependency injection was weird. Then I came to realize that TypeScript interfaces are meeheed out during transpilation.
Digging into the documentation I found about custom providers that could somehowemaybekinda work through. But in the end it requires far too much and items that well, they just don't feel as natural as if I was writing this in C# or Java, or PHP (actually where I use it the most)
I still think it is a framework worth learning, but I believe that this might be a bias of mine of deriving from the norm to which I was and have been used to doing the most.3 -
What's the best nodejs framework for the MEAN stack? I need to do additional things to put TypeScript in node js and express. I have seen nestjs with a good directory structure and also uses TS by default. How about meteor or Koa?
Should I just add TS to my existing node and express? Or use nestjs or some other nodejs framework. What do you suggest?3 -
So I'm new to NestJS, Node, etc. and I just noticed that the guy working on the API made every request call a different service class, instead of using a single service class. For example.
get() {
return await this.getObj.run()
}
post(myDto){
return await this.storeObj.run()
}
update(myDtoUpdate){
return await this.updateObj.run()
}
And I'm not sure why. He's also injecting the request into those classes, instead of passing the DTO to the method call. I mean, it's still injecting the data into it I guess, but it seems so roundabout. Something like this:
public constructor(
@Inject(REQUEST) private request: Request,
){}
I'm scared, but I'm not sure if it's just my own ignorance or a sixth sense telling me that this is gonna be a mess.
Have you seen APIs implemented this way? I can see the benefit of dividing the code into smaller classes, but it just seems overkill to me, specially when there's a big chance that code will be repeated (getting an entity by ID when updating it, for example).
I'm still in time to kill this with fire before a new monster is born though, so that's something.1 -
Help me decide to choose between nestjs and Adonis js framework for node? I know laravel and angular so it makes hard for me to choose between the two.
Nestjs is angular inspired while Adonis js is laravel inspired. I only have experience with express framework. Thanks!3 -
Is NodeJS + Express + Sequelize enough for an Enterprise app from scratch. Or should I use other Node frameworks like AdonisJS or NestJS?
Frontend will be Angular 9. Database will be MySQL. Thanks!12