Luciano Mammino 𝕏 Node.js Design Patterns @loige

#AWS #Serverless Hero & MVP. Senior Architect @fourTheorem, author of 📕 https://t.co/Vhhe4G4GCN & ✉️ https://t.co/XMK2BWythj #Nodejs, #JavaScript, #Rust 🦀 & #Cloud ☁️ loige.co eu-west-1 Joined April 2009

Tweets

36K
Followers

10K
Following

6K
Likes

35K

Luciano Mammino 𝕏 Node.js Design Patterns @loige

5 days ago

@jenewland1999 💯! I was going to put a graph of the new release timeline (like the one in the official site) in the article but then I realized the new approach makes things so easy that a timeline is pretty much superfluous! The Node.js community is truly awesome! 😎

0 0 2 229 0

View Details

Luciano Mammino 𝕏 Node.js Design Patterns @loige

6 days ago

🎉 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 250 49K 38

View Details

Luciano Mammino 𝕏 Node.js Design Patterns @loige

6 days ago

💚 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/blog/nodejs-re… #nodejs #javascript

0 1 17 3K 3

View Details

Luciano Mammino 𝕏 Node.js Design Patterns @loige

6 days ago

♻️ 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 0 28 4K 1

View Details

Anthony Bouch @58bits

2 weeks ago

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

7 6 51 9K 51

View Details

Luciano Mammino 𝕏 Node.js Design Patterns @loige

a month ago

Node.js 26 shipped this week 🎉 My birthday is close, so I'm officially calling it an early birthday present from the Node.js team 😂 It doesn't look flashy at first, but the additions are genuinely useful in everyday code. I wrote a code-heavy tour, here's what stood out 🧵

1 1 19 1K 2

View Details

Luciano Mammino 𝕏 Node.js Design Patterns @loige

a month ago

The article shows the new API side-by-side with the old one for every feature, plus a companion GitHub repo with every snippet ready to clone and run. I hope you'll like it 🙂 nodejsdesignpatterns.com/blog/whats-new…

0 2 8 426 1

View Details

Luciano Mammino 𝕏 Node.js Design Patterns @loige

a month ago

Plus the cleanup: private _stream_* modules, http.Server.writeHeader(), and --experimental-transform-types are gone. module.register() is runtime-deprecated. If you maintain libraries, this is a good time to grep for those.

1 0 3 166 0

View Details

Luciano Mammino 𝕏 Node.js Design Patterns @loige

a month ago

New post: Writing middlewares for #Rust #Lambda functions 🦀 The #AWS Lambda Rust runtime already ships a middleware engine: tower. Almost nobody is using it. Deep dive + a complete #DynamoDB rate limiter you can steal: loige.co/writing-middle…

1 2 4 488 1

View Details

Luca Palmieri @algo_luca

a month ago

Little update on my reflection adventures: I have extracted the core components of Pavex's compile-time reflection engine as a set of standalone crates! It serves as a preliminary step ahead of another release in the coming weeks 🛠️

2 1 23 2K 4

View Details

Luciano Mammino 𝕏 Node.js Design Patterns @loige

a month ago

PS: the post is sprinkled with rabbit holes 🐇, curious deep dives into things like async fn in traits, hand-rolled futures, fixed window vs token bucket, why `CorsLayer` works on Lambda, and more. Make sure to click into some of them. Just try not to get lost in them 😉

0 0 0 81 0

View Details

Luciano Mammino 𝕏 Node.js Design Patterns @loige

a month ago

All the code lives at: github.com/lmammino/rust-… Clone it, `sam deploy`, and you are 5 minutes away from a working tower-based rate limiter on AWS. Let me know what you build with it 👀