
Open Source enthusiast, #NestJS, #Angular, #Typescript, and #Node. Author of #Ogma, #nest-commander, and @nestjs/throttler. Software Architect at @trilon_io
Washington, USA
Joined July 2012
- Tweets94
- Following28
- Followers324
- Likes127
jmcdo29 retweeted
🎉 Celebrate the big cross over 60k 🎉
Show @nestframework some ❤️ and ⭐️ it if you haven’t yet!
Thanks to all the years of support, and to many more!
#nodejs #nestjs #typescript
jmcdo29 retweeted
Version 10 of @nestframework is finally here! 🚀
trilon.io/blog/nestjs-10-is-…
jmcdo29 retweeted
📝 New @nestframework article LIVE!
Let's learn how we can make our #NestJS applications more "data source agnostic" ⚙️
Letting us switch between data sources seamlessly without making any changes to the business logic and the entire application.
trilon.io/blog/implementing-…
Gah! I just need a moment to mention how cool @NxDevTools is! Just wrote a custom executor to build docker images with tags and targets generally based on npm scope and project name with overridable configs for a new project I'm working on. Super simple to setup.
1
4
481
jmcdo29 retweeted
NEW @nestframework blogpost live! 📯
Learn about NestJS WebSockets Messages and RxJS Subjects - by Trilon's @jmcdo29
trilon.io/blog/nestjs-websoc…
nest-commander just passed 300 stars on GitHub! Always excited to see this getting used in the wild. Thanks for all the stars and feedback so far #Nest @nestframework #opensource github.com/jmcdo29/nest-comm…
8
1,312
jmcdo29 retweeted
Such an amazing and in-depth article by @thiagomni, check it out! 📚
🎉 NEW article published!
Applying Test-Driven Development (TDD) with @nestframework ⚡️
By Trilon's @thiagomni 🔥
trilon.io/blog/tdd-with-nest…
jmcdo29 retweeted
🎉 NEW article published!
Learn about circular dependencies, how they work in NestJS, and how a tool like Madge can help you detect them!
By Trilon's @jmcdo29
trilon.io/blog/avoiding-circ…
jmcdo29 retweeted
Replying to @nestframework
@nestframework just hit 2M downloads/week 🎉🤯
Thanks to all the years of support, to many more!
#nodejs #nestjs #typescript
Rewrote my docs for Ogma using @astrodotbuild and gotta say I loved the process. Deployment was a breeze and I only needed a few modifications coming from docusaurus. Keeping it all in my @nrwl_io nx monorepo and deployed to @GithubPages
jmcdo29 retweeted
📯 New Article out on the @trilon_io blog!
📝 #NestJS Swagger API Documentation Tip and Tricks by Trilon's - Ilya Moroz
trilon.io/blog/nestjs-swagge…
jmcdo29 retweeted
Nest has just advanced to "Adopt" in @thoughtworks' Tech Radar in its 2022 edition (volume 27) 🔥🎉
thoughtworks.com/radar/langu…
jmcdo29 retweeted
Volume 27 of the Technology Radar is finally here! Want to know which blips our Technology Advisory Board included this time? Download the report today for all the #tech trends you need to know. #TWTechRadar thoughtworks.com/radar?utm_s…
jmcdo29 retweeted
NEW Article out on today! 📯
"Fundamentals of Automated Testing - Unit Tests Basic Concepts" by @deluccadev from @trilon_io
trilon.io/blog/fundamentals-…
jmcdo29 retweeted
Congrats to nestjs/nest, which has grown by 235 stars in the last 7 days and has reached 51.6K stars.
Thanks to the contributors: @kammysliwiec @brunnerlivio @jmcdo29 @wilsonsaccount @kznvc
ossinsight.io/analyze/nestjs…
#TypeScript
jmcdo29 retweeted
The #TypeScript compiler might not be the fastest - but why is that such a big problem?
"We have a large project" - I get that, but there are other things you can do that will impact development speed and DX:
jmcdo29 retweeted
TypeScript tip:
Avoid making a property optional when the property isn’t valid in a certain case.
Instead, declare 2 separate types, and use Omit to avoid copy/paste.
Example: Many objects lack an id until they're saved. So declare a separate "Unsaved" type.
#typescript

ALT // Avoid making a property optional to support two separate scenarios. // Doing so redunces type safety. type User = { // Making id optional since unsaved users don't have an id yet. 👎 id?: number; name: string; email: string; } // Instead, declare separate types. Then each scenario is fully type safe. 👍 type User = { id: number; name: string; email: string; } // Separate type for unsaved users. // Deriving from the User type via Omit to keep types clean and lean. type UnsavedUser = Omit<User, "id">;
New open source pet peeve I've found: users expecting major library upgrade available the day they are released and opening an issue in the library when the framework doesn't support the new version yet. Like, give us time to upgrade first jeez #oss #petpeeve #seriously














