Practica - Node.js Best Practices
@nodepractices
Followers
13K
Following
468
Media
154
Statuses
416
A family of repositories about Node.js practices including a starter project (100k stars β¨): - https://t.co/SlWaXArx3q - https://t.co/RGbavsSUmu
Joined June 2016
π₯Ή We're happy to launch our 'official' starter: Practica.js What's unique about it? 90 seconds video π TL;DR: Zero abstractions, simple as JS meant to be, development and production-ready. Based off our guide 'Node.js best practices Start using it: https://t.co/tZ0qvfUFTe
0
15
53
From the Node.js security master π
Node.js Secure Coding is going to be the most comprehensive and packed application secure coding resources you'll find for backend Node.js development π€© Starting with Command Injection! It's at 30% sale off for the summer, grab it while you can π· https://t.co/2BM0HZF8G4
2
3
25
π₯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 https://t.co/nyj1xd7lWg
github.com
:white_check_mark: The Node.js best practices list (July 2024) - goldbergyoni/nodebestpractices
0
24
59
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) https://t.co/nyj1xd6O6I
0
2
17
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
0
2
14
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: https://t.co/s4b1yJNYdJ
0
4
8
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 π. https://t.co/nmhKyp46WD
1
7
14
πββοΈπ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? https://t.co/8ZnahF2QJx
practica.dev
Where is our focus now?
1
5
17
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 β€οΈ https://t.co/xpmkfCMo78
16
10
117
πA new blog post by our team
If you keep hearing the name 'Prisma', have that fear of missing out feeling, and are curious whether it's a true game changer in the JavaScript ORM space, my new article might be of interest: Is Prisma better than your 'traditional' ORM? https://t.co/epp1kSmt7e
0
0
2
Say a component must initialize a variable before allowing access to any other function (E.g., DB connection), what pattern should we use then?
3
0
1
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: https://t.co/OM3ErnmZrp
1
0
5
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."
3
2
27
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
0
0
9
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? https://t.co/mCRJ0tH392
0
2
2
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? https://t.co/tZ0qvfUFTe
0
1
8
@goldbergyoni 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!
π 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 https://t.co/eMc6b6T2Dx
0
2
10
π 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 https://t.co/eMc6b6T2Dx
3
7
34
βοΈ 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 https://t.co/q31ZQ8DoDL
practica.dev
Node.js is maturing. Many patterns and frameworks were embraced - it's my belief that developers' productivity dramatically increased in the past years. One downside of maturity is habits - we now...
3
10
41
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?
5
2
18