@teffcode@jsconfes@NodeSource Ojalá @jconfes pueda liberar las charlas, en su canal de youtube. en un mundo globalizado dificil entender que ese conocimiento no pueda ser compartido. Bien @teffcode no dudo del gran aporte que das a la comunidad junto con grandes speaker!
Gracias infinitas a toda la comunidad de @jsconfes 💛 Un honor poder compartir con todos y con todas ustedes el día de hoy !!!
Thanks to @NodeSource for sponsoring events like this that bring the tech community together and help advance education, innovation, and collaboration in technology. #JSConfES 💛
Hi everyone ! 💛☺️
Sharing the slides from my talk “Node.js por dentro: entendiendo el runtime en producción” at JSConf Spain, in case you’d like to revisit them or explore any of the ideas further 👇🏼
canva.com/design/DAHD6hC…
Thank you so much for the amazing energy, conversations, and curiosity during the session, it truly meant a lot.
If you have any questions or thoughts, please don’t hesitate to reach out. Always happy to continue the conversation ! 🚀
Speakers dinner tonight in Spain 🇪🇸🍽️
@erickwendel_ and @teffcode from NodeSource sharing a great evening with fellow speakers and getting ready for tomorrow at @jsconfes 🚀
Excited for the talks, the community, and all the JavaScript energy. See you tomorrow! ⚡ #JSConfES
Still running an End-of-Life Node.js version? ⚠️
Here’s a safer way to upgrade in production:
1️⃣ Scan your app
2️⃣ Analyze upgrade risk
3️⃣ Execute with a clear plan
Run the free scan:
npx @nodesource/upgrade
Your code never leaves your machine.
Start here 👇🏼
🟢 Open-source project powering production Node.js environments.
If you run Node.js in production, your runtime shouldn’t be a black box.
Most teams monitor the app.
Few truly govern the runtime.
N|Solid is an open-source, cross-platform runtime based on Node.js — built for production visibility.
Learn more:
👉🏼 https://t.co/Vz1qPAawHN
730,694 downloads
45,325 commits
4,243 contributors
Inspect the code:
👉🏼 https://t.co/uJEiRKZovL
Production-grade systems start at the runtime.
#NodeJS#Backend#DevOps#OpenSource
If you run Node.js in production, this will resonate:
👉🏼 nodesource.com/blog/from-cpu-…
🔹 CPU spike.
🔹 You generate a profile.
🔹 Thousands of frames.
🔹 Deep V8 stacks.
🔹 High self-time hotspots.
You know something is slow.
But what do you change?
And how do you prove it’s better?
This breakdown shows how N|Sentinel:
• Identifies the true bottleneck
• Retrieves contextual source code
• Generates an optimized version
• Benchmarks it automatically
• Validates measurable improvement
Not just observability.
Intelligent remediation.
For serious Node.js production teams, this changes the workflow.
#NodeJS#Backend#PerformanceEngineering#Observability#DevOps
🎬 What happened this week in Node.js?
For production teams:
🔹 Node.js 24.13.1 (LTS)
🔹 Node.js 25.6.1 (Current)
For the community:
🔹 Node.js Collaboration Summit 2026 H1 → London 🇬🇧
Patch releases keep production stable.
The Summit is where contributors align on the future of Node.js.
🔗 Links:
· v24.13.1 (LTS)
nodejs.org/en/blog/releas…
· v25.6.1 (Current)
nodejs.org/en/blog/releas…
· Collaboration Summit 2026 H1
github.com/openjs-foundat…#NodeJS#OpenJS#JavaScript#Backend
Is Node.js single-threaded… or not? 👀
We just published an animated blog breaking this down step by step:
👉🏼 nodesource.com/blog/is-nodejs…
With a couple of concrete examples:
• setTimeout
• crypto.pbkdf2
• V8 vs libuv
• Thread pool vs main thread
If Node.js threading has ever felt confusing — this will make it click ⚡
🎬 What happened this week in Node.js?
A quick recap of the most relevant updates for teams running Node.js in production:
🔹 New official codemod: Chalk → util.styleText
🔹 Node.js 25.6.0 (Current) is out
🔹 Lodash completes a major security reset
🔗 Links to each update:
·