Luciano Mammino 𝕏 Node.js Design Patterns@loige

#AWS #Serverless Hero & MVP. Senior Architect @fourTheorem, author of πŸ“• nodejsdp.link & βœ‰οΈ fstack.link #Nodejs, #JavaScript, #Rust πŸ¦€ & #Cloud ☁️

 eu-west-1
loige.co
Joined April 2009
2,992 Photos and videos
πŸŽ‰ Big news and a gift for you 🎁 Keep readingπŸ§΅πŸ‘‡
Close-up of a person in a black leather jacket holding the 4th edition of β€œNode.js Design Patterns” by Packt, featuring a black cover with a purple wave graphic and small author headshots (Luciano Mammino and Mario Casciaro), against a light brick background.

ALT Close-up of a person in a black leather jacket holding the 4th edition of β€œNode.js Design Patterns” by Packt, featuring a black cover with a purple wave graphic and small author headshots (Luciano Mammino and Mario Casciaro), against a light brick background.

1
6
46
4,431
Tonight i had the weirdest dream of seeing @antirez and @badlogicgames playing tennis table and they were too damn good! πŸ™ˆ What do I make of this? Either I like software (and some of the influential people around it) way too much, or I need to see a shrink... Or probably both!
2
526
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
SolidJS@solid_js
Aug 13
🚨 Solid 2.0 has reached Release Candidate! πŸŽ‰πŸ₯³ Async is first-class β€” computations return promises, the graph suspends and resumes itself. Plus optimistic mutations and a reactive core rebuilt from scratch. The Big <Reveal> πŸ‘‡ solidjs.com/blog/solid-2-0-r… 1/3
36
152
1,171
232,564
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
Ryan Carniato
@RyanCarniato
Aug 13
It's finally here! So many thoughts/feelings I couldn't fit them in the blog post but its crazy to think after so much work this is only the beginning.
SolidJS@solid_js
Aug 13
🚨 Solid 2.0 has reached Release Candidate! πŸŽ‰πŸ₯³ Async is first-class β€” computations return promises, the graph suspends and resumes itself. Plus optimistic mutations and a reactive core rebuilt from scratch. The Big <Reveal> πŸ‘‡ solidjs.com/blog/solid-2-0-r… 1/3
22
34
603
46,611
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
Luciano Mammino 𝕏 Node.js Design Patterns@loige
Jul 6
Environment variables in Node.js look trivial until they bite you: everything is a string, "false" is truthy, and every child process you spawn inherits your secrets. I just published a complete guide. Here's the short version 🧡
Infographic titled β€œNode.js Environment Variables: Simple until they bite you.” On a dark, neon green and cyan tech-style background, five panels explain key pitfalls and best practices: (1) everything in process.env is a string, for example PORT becomes "3000"; (2) the β€œfalse” trap, where "false" is still truthy in JavaScript; (3) built-in .env loading in modern Node.js with --env-file; (4) layered .env files, where later files win but OS environment variables still override; and (5) security risks, showing child processes inheriting secrets by default. A green banner at the bottom highlights the best practice: use one validated config module, fail fast, and keep secrets out of environment variables in production. The full guide URL appears at the bottom: nodejsdesignpatterns.com/blog/nodejs-environment-variables.

ALT Infographic titled β€œNode.js Environment Variables: Simple until they bite you.” On a dark, neon green and cyan tech-style background, five panels explain key pitfalls and best practices: (1) everything in process.env is a string, for example PORT becomes "3000"; (2) the β€œfalse” trap, where "false" is still truthy in JavaScript; (3) built-in .env loading in modern Node.js with --env-file; (4) layered .env files, where later files win but OS environment variables still override; and (5) security risks, showing child processes inheriting secrets by default. A green banner at the bottom highlights the best practice: use one validated config module, fail fast, and keep secrets out of environment variables in production. The full guide URL appears at the bottom: nodejsdesignpatterns.com/blog/nodejs-environment-variables.

Made with AI
1
1
4
651
Environment variables in Node.js look trivial until they bite you: everything is a string, "false" is truthy, and every child process you spawn inherits your secrets. I just published a complete guide. Here's the short version 🧡
Infographic titled β€œNode.js Environment Variables: Simple until they bite you.” On a dark, neon green and cyan tech-style background, five panels explain key pitfalls and best practices: (1) everything in process.env is a string, for example PORT becomes "3000"; (2) the β€œfalse” trap, where "false" is still truthy in JavaScript; (3) built-in .env loading in modern Node.js with --env-file; (4) layered .env files, where later files win but OS environment variables still override; and (5) security risks, showing child processes inheriting secrets by default. A green banner at the bottom highlights the best practice: use one validated config module, fail fast, and keep secrets out of environment variables in production. The full guide URL appears at the bottom: nodejsdesignpatterns.com/blog/nodejs-environment-variables.

ALT Infographic titled β€œNode.js Environment Variables: Simple until they bite you.” On a dark, neon green and cyan tech-style background, five panels explain key pitfalls and best practices: (1) everything in process.env is a string, for example PORT becomes "3000"; (2) the β€œfalse” trap, where "false" is still truthy in JavaScript; (3) built-in .env loading in modern Node.js with --env-file; (4) layered .env files, where later files win but OS environment variables still override; and (5) security risks, showing child processes inheriting secrets by default. A green banner at the bottom highlights the best practice: use one validated config module, fail fast, and keep secrets out of environment variables in production. The full guide URL appears at the bottom: nodejsdesignpatterns.com/blog/nodejs-environment-variables.

Made with AI
1
1
4
651
more replies
NODE_ENV=production does not make your app faster by itself. ... BTW It's a convention, not a Node.js feature. It just tells your dependencies (Express, React, bundlers) to behave like production. If they don't check it, nothing changes.
1
1
92
The pattern that ties it all together: one config module, validated at startup, fail fast. The rest of the code never touches process.env directly. Full guide (validation with Zod, security, NODE_DEBUG and friends): nodejsdesignpatterns.com/blo…

Environment Variables in Node.js

Learn how to use environment variables in Node.js with process.env, the native --env-file flag, validation, and security best practices.

nodejsdesignpatterns.com
2
93
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
Luciano Mammino 𝕏 Node.js Design Patterns@loige
Jun 5
πŸŽ‰ Big news: Node.js is changing its release schedule for the first time in 10 years. From October 2026, less to remember and easier to know what's Current or LTS. Here's everything you need to know πŸ§΅πŸ‘‡
2
23
247
49,493
πŸŽ‰ Big news: Node.js is changing its release schedule for the first time in 10 years. From October 2026, less to remember and easier to know what's Current or LTS. Here's everything you need to know πŸ§΅πŸ‘‡
2
23
247
49,493
more replies
♻️ Every release becomes LTS. No more "wait, is it odd or even?" πŸ™ƒ πŸ§ͺ A new Alpha channel (27.0.0-alpha.1) gives library authors a 6-month window to test breaking changes early.
1
27
3,706
πŸ’š Best part: it's the project simplifying itself to match how people actually use it, and easing the load on the volunteers who keep Node.js alive πŸ™ Full breakdown here πŸ‘‡ nodejsdesignpatterns.com/blo… #nodejs #javascript

Node.js is changing its release schedule and version numbers

Node.js is moving to one major release a year, year-based version numbers, every release becoming LTS, and a new Alpha channel. Here is what changes.

nodejsdesignpatterns.com
1
16
3,386
Luciano Mammino 𝕏 Node.js Design Patterns retweeted
Anthony Bouch
@58bits
May 25
Introducing Byline CMS: We've spent more than a year working on Byline, a new open-source headless CMS, with our reference implementation built on TanStack Start and PostgreSQL. While it's still early, we thought the project might be in good enough shape now to give anyone wanting to take a closer look a pretty good idea of how Byline was designed and built. Links to the repo and to the site with very early machine-generated docs are in the comments below (the docs aren't great). We started work on Byline for a few reasons, the main one being that we wanted to provide our customers with a platform that was a better fit for the work they do, in particular with respect to content language translation, document versioning and workflow. You can read more about our take on this in the Mission / Vision section in the repo README or on the site. In terms of timing, I suspect that if we'd posted this in 2024 - it might have generated a little more excitement than it likely will today - amid the firehose that is all things AI. That said, we've also benefited significantly from the latest coding agents and LLMs - Claude Code in particular. We designed the core storage system and collection schemas by hand, well before the 'big lift' in AI coding agent capabilities that happened late November last year. Since then we've used Claude extensively to help make progress. We've talked about this a bit more in our docs and README as well. We've also included what we think is a pretty good AI-assisted editor via our AI package. If only one other developer or agency decided to take a closer look, that would be great. We would very much appreciate an extra pair of eyes or two. There's still plenty to do, and we've almost certainly made mistakes. Feel free to DM me if you have any questions, would like to know more, or would even be interested in a call or a demo. Hope a few of you out there like Byline as much as we do. Will try to get an introductory video up as well soon. Oh and a hat tip to the folks at Payload CMS as we were inspired by a lot of the great work done there. @tannerlinsley @matteocollina @sebastienlorber @jacobsfletch @AlessioGr #tanstack #react #opensource #headlesscms #typescript #postgresql #contentmanagement
An image of the landing page of Byline CMS - a new headless CMS.

ALT An image of the landing page of Byline CMS - a new headless CMS.

7
6
51
8,914
Load more