Thought - I would avoid using the popular ENV='prod'|'dev'|etc It encourages different code branches per specific environments Instead, use specific variables for specific features, e.g. 'PRETTY_PRINT' will be assigned 'TRUE' within Dev command Does it make sense?

✏️ So happy to share my new blog post: "Popular Node.js patterns and tools to RE-consider" Examples: .env, supertest, log from catch(), Nest DI, 'fat' services, and more It's not about good vs bad, rather the right context and alternatives practica.dev/blog/popular-n…

🎉 Video of the Testival: One session, 8 speakers, each one had 3 minutes (!) to share insightful Node.js testing tip I tried a unique conference talk format. Based on the audience score, they really liked it p.s. Never dare miss the last tip, 33:12 youtube.com/watch?v=o5sLLY…

Yoni Goldberg struck gold with this format. What the audience got were small and practical pieces of information that they can easily implement in their work. I love this format (as did the audience!) and I hope other conferences will pick it up and try it!

From our starter Practica.js - The 'use-case' pattern This file is called by the controller and provides a high-level summary of the flow. It prevents unnecessary complexity from the reader who can choose where to focus Like it? Have concerns with this? github.com/practicajs/pra…

We're working to finalize our .Dockerfile, help us choose the right base image? Like any other decision, a comparison table is shared and the community thoughts directly affect the decision Do we miss any consideration here? practica.dev/decisions/dock…

We're growing slowly and steadily: 29 contributors, ~1200 downloads per month, 400 stars Practica.js is a new way of coding Node.js apps that is all about simplicity

GitHub and npm team doubles-down on maintainer security: "Starting today, two-factor authentication (2FA) will be enforced for maintainers of all high-impact npm packages: more than 1 million weekly downloads or have more than 500 dependents."

We're evaluating ORMs for practica.js (our Node.js starter), an empirical comparison is always preferred Which ORM has the best docs? With regard to comprehensiveness, Prisma seems to be on top 👇 Full conclusions will follow Other decisions: practica.dev/decisions/

Say a component must initialize a variable before allowing access to any other function (E.g., DB connection), what pattern should we use then?

🎉A new blog post by our team

Node.js Design Patterns (the book 📙) is currently #9 in the WebServices category and #15 in the JavaScript category on Amazon! I am really proud of these results! 🤩 Thanks to everyone who has kindly left us a review ❤️ nodejsdesignpatterns.com

🙋‍♀️🎉Happy to share that Practica.js v0.0.6 is out 🤗 With new features like a hardened .dockerfile, request-level store, additional ORM option: Prisma, and more Use it as the starter for your next Node.js project? practica.dev/blog/practica-…

Recently we had a great opportunity to present at a BudapestJS community meetup on how to write #FullStack #TypeScript code without repeating yourself. We've even live-tested an upcoming pre-release feature - Live Query 🎉. youtu.be/op32k0_3Fjs

Backend testing arrived at a stage where testing the blue area, user flows with all the layers, is straightforward. Great With the same tools we should also cover the edges which hide many significant risks This is what my new blog post is about: practica.dev/blog/testing-t…

2023 edition of our repository will get released on Tuesday next week. Working to cover strategic new Node.js features, here is a sneak peek

Tomorrow we will release the 2023 edition of Node.js best practices Here is another sneak peek into content that was modernized and refers to new platform concepts (e.g., EventTarget) github.com/goldbergyoni/n…

🥄Ding ding ding, announcement: The 2023 edition of Node.js best practices is out 🎊 What's new: - New practices about new techniques like ESM, EventTarget, etc - Recommended libs for 2023 - Skim through the #new or #updated tags for new content only github.com/goldbergyoni/n…

From the Node.js security master 👇