Grug, uma pergunta: você acha que vale a pena DI em Node? Não digo com aquelas nojeiras de libs de DI (tsyringe e inversify) que aí é melhor fazer na mão mesmo. Ou acha que nem vale a pena visto que o Node é singleton por padrão?

Inversify永遠にわからんすぎて絶対記事書く

E aquelas libs pra container DI: tsyringe, inversify 💀 kkkkkkk tenebrosas bicho. E quando não é isso é alguma lib interna que alguém cria que não faz porra nenhuma a não ser fazer um "wrapper" e tu ainda precisa fazer tudo manual

Having removed horrible messes caused by Inversify and friends from codebases at two companies, I’d recommend passing explicit dependencies as arguments.

We use inversify. We are fully serverless and serve 100k users daily with no dramas. Easy to maintain and debug.

プログラミング14年目にしてテストの勉強中 DIコンテナ inversifyは便利「実体ではなく抽象に依存する」この思想はGood 例) ・コンセントは「電気を流すことだけ」に関心があり、レンジや冷蔵庫には関心がない ・忍者は「武器」に関心があり、手裏剣や刀に依存しない=差し替え可能 #typescript

While legacy decorators are not part of the spec, they are still practically better than the ES decorators. I think, we would want to gracefully move to ES decorators once they implement support for the context. Right now without context, ES decorators are useful for very limited use-cases. Btw, legacy decorators should never be removed, unless TypeScript wants to blow up the entire ecosystem of TypeORM, NestJS, MikroORM, Inversify and so on.

Market is so bad these days but we eat good at 888 lounge 💰💰👊! I'm feeling generous now and You can join for free 👀 (It's cost 6SOL ) t.me/hashtcalls Tg will closes in 72hrs 🚫! 🔖 Also don't forget to follow : @dorkifreak 🏰 888 Lounge 📊 Group Stats ├ Period: 1d └ Return: 80.0x (Avg: 5.0x) 🚀💊 1 $Y/N » esunnnn [69.7x] 😎💊 2 $TIME » esunnnn [13.8x] 😎🟣 3 $78 » esunnnn [13.1x] 😎🟣 4 $PANICAN » esunnnn [2.7x] 😎🟣 5 $MIRACLE » esunnnn [2.4x] 😎💊 6 $INVERSIFY » esunnnn [2.1x] 😎🟣 7 $FFM » esunnnn [2.0x] 🥱💊 8 $Pepeometry » esunnnn [1.2x] 🥱💊 9 $ALT » esunnnn [1.2x] 🥱🟣 10 $移动 » esunnnn [1.2x]

INVERSIFY 😂

company rules, man, before this was a inversify type shit

You can use DI containers like TSyringe or inversify. Those work pretty well. They can work with or without decorators but need reflect-metadata.

memo. クラスベースの DI をするやつ。 [inversify/InversifyJS: A powerful and lightweight inversion of control container for JavaScript & Node.js apps powered by TypeScript.](github.com/inversify/Inversi…)

Quanto ao Nest, acho que, se for o padrão da codebase, n tem jeito 🤣 Mas TSyringe, Inversify ou qualquer maluquice que inventem para DI, eu já acho over. Primeiro que esses caras aí nem têm suporte ativo mais, a maioria está abandonada. Aí você vai enfiar na tua codebase uma( )

Release free course baru untuk semua student Devscale. Ada 3 Courses : - Layered Architecture Elysia.js. Belajar bikin backend Elysia Prisma dengan Layered Architecture, pakai Model Dependency Injection dengan Inversify. - Building Backend without Code - Pocketbase. Belajar Deploy Pocketbase ke Server, Setup CRUD dengan Nextjs, Authentication dan Oauth Google. - Building LLM Crawler. Bikin scrapper, crawler dan LLM Processing untuk generate cuman dengan input domainnya aja. Pakai Nextjs of course. 🥱 Siapapun yang pernah belajar di Devscale, Beli Course di Aku/Devscale, Feel free to Enroll it.

TypeScript에서 DI 관련 라이브러리 중에 Inversify 가 기능이 풍부하네. Spring Framework 사용에 익숙하다보니 설정도 간편하고 표현도 직관적이고 러닝 커브도 낮은 TypeDI를 우선 쓰기로 했다.

There are a few projects trying it (tsyringe or inversify), but the absence of decent annotations makes it harder. Tbh I got disappointed in dependency injection in Java as well when compared to symfony or laravel

TsyringeとInversifyの両方でtsのdi container試してみる

NestJSは好きなのだが、Node.js/Expressでも型化してしまえばそれでも良いかなと。 アーキパターンを取り入れて、DIはinversify入れて、共通なエラハンはRestControllerAdviceのようにAllExceptionFilterのような機構を作って全体に入れてあとはレイヤーの責務に沿って作るようにしている

I went to a wizard school today, I can’t believe they don’t teach inversify anymore, apparently it’s “outlawed” for some reason??

I’m telling you now, if you’re in my gold cave again, I’m gonna fucking inversify you