John Agudelo

👨🏻‍💻🇨🇴 😊 node js backend developer

[Estefany Aguilar @teffcode]

Comunidad de Node.js 💚📢

Quisiera conocer su opinión sobre las extensiones de VS Code para Node.js y, especialmente, sobre una nueva que lanzamos la semana pasada en @NodeSource 👀

Se llama N|Solid in the IDE y permite visualizar métricas, diagnósticos y runtime telemetry de aplicaciones Node.js directamente dentro de VS Code ⚡️

Por ejemplo:

· detectar problemas del Event Loop,
· analizar CPU profiles,
· revisar heap snapshots,
· y entender runtime events en tiempo real sin salir del editor.

Me encantaría que la pudieran instalar, probar y contarme honestamente:

· qué les parece útil,
· qué mejorarían,
· qué les gustaría ver,
· o cómo encaja en su flujo de trabajo actual.

Pueden dejar su comentario directamente en el hilo de este mensaje o, si prefieren, dejar feedback anónimo aquí 👉🏼 https://t.co/V5bxFDyiV3

Extensión:
https://t.co/xFdsI7csTZ

Les agradecería mucho si pueden compartir esto con más Node.js Devs ! 😉🚀

[NodeSource @NodeSource]

Big announcement 🚀

We just launched the N|Solid Extension in the IDE at #WebSummitVancouver 🇨🇦.

For years, developers have been stuck in a broken workflow:

leave the IDE → open dashboards → investigate production → return to code → guess at a fix.

That context switching has become one of the biggest bottlenecks in the AI era.

The N|Solid Extension in the IDE changes that by bringing live production telemetry and pre-commit validation directly into VS Code.

⚡ Live runtime telemetry in the IDE
⚡ AI-powered incident analysis
⚡ Pre-commit fix validation
⚡ One-click profiling & remediation

No more disconnected dashboards.
No more guessing.

Production truth. Right where you code.

Press:
🔗 https://t.co/gW8ROe9DOZ

VS Code Extension:
🔗 https://t.co/nWbS7XVdsK

#NodeJS #VSCode #AI #JavaScript #Observability #WebSummit #DeveloperTools

[NodeSource @NodeSource]

We’re excited to be at #WebSummitVancouver next week 🇨🇦 especially because we have something big to announce 🎉

Live production runtime intelligence, directly into IDEs.

Today, our CEO, @russwhitman, shares what this means — and what’s coming next for the future of observability in @nodejs.

See you at Web Summit! The countdown is on 🥳

#NodeJS #Observability #FindTheMissingLink

[NodeSource @NodeSource]

As we get closer to #WebSummitVancouver…

Today, @brycebaril — Node.js expert — shares a real debugging frustration:

IDE → dashboards → logs → back again…
just to understand one issue.

Too much context switching.

See you there 🇨🇦

#NodeJS #DevTools #Observability #AI

[NodeSource @NodeSource]

Big announcement 🚀

NodeSource joins the @openjsf Foundation’s LTS Upgrade & Modernization program.

Too many enterprises are still running legacy or EOL Node.js versions, creating real security and compliance risk.

We’re changing that with a secure, AI-powered upgrade path:
Scan → Analyze → Execute.

And as inaugural partner, we’re sharing 15% of program revenue to support the @nodejs ecosystem.

Press:
🔗 https://t.co/IM1ijuUEsC

Program:
🔗 https://t.co/T9NAoHn9r3

#NodeJS #OpenJSFoundation #UpgradeProgram

[NodeSource @NodeSource]

If you run Node.js in production, this will resonate:
👉🏼 https://t.co/ko3t9uhdSj

🔹 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

[Alicia Informa al Pueblo @Roja53C]

La mejor explicación del show de Bad Bunny para los que no entendieron y critican su actuación ...

[Bleacher Report @BleacherReport]

Bad Bunny's football to close his Super Bowl halftime show: “Together, We Are America.”

[NodeSource @NodeSource]

✅ Resolved

Seeing GPG error: NO_PUBKEY on Debian 13 or modern Ubuntu?

It's not a broken setup, it’s a repo timing issue.
We explain what's happening and the safe workaround until official support lands.

👉🏼 Full breakdown here: https://t.co/PswJmvIaix

[NodeSource @NodeSource]

If everything is critical, nothing is.

CVEs and CVSS show up everywhere in security dashboards, but many teams still use them the wrong way.

CVE tells you what exists.
CVSS tells you how severe it is in theory.
👉🏼 You decide what actually matters.

Read the full breakdown 👇🏼
https://t.co/T8aeiS1MFX

#NodeJS #Security #DevSecOps #SoftwareEngineering

[Carlos Santana @DotCSV]

🔮 ¡MIS PREDICCIONES IA del 2026! 🔮

Un año más aquí os traigo 24 ideas de lo que creo podría pasar en el mundo de la Inteligencia Artificial durante este año

24 predicciones que podéis votar y apoyar una a una usando el botón 💖

¡Comparte el hilo! En 12 meses verificamos 😄👇

[NodeSource @NodeSource]

Node.js January 2026 Security Release 🛡️

What changed and why it matters for production.

We break down the most important fixes across memory safety, permissions, HTTP/2, and TLS so you know exactly what to pay attention to.

Read the full post 👇🏼

https://t.co/QnnnIsuC76

[NodeSource @NodeSource]

require(esm) didn’t become stable because ESM “won.”

It became stable because Node.js learned how to evolve without breaking the ecosystem.

This timeline is less about syntax and more about backward compatibility, scale, and incremental adoption.

#NodeJS #JavaScript #SoftwareArchitecture

[John Agudelo @jd4ison]

@emanueledpt I prefer an M4 with 36 or more RAM

[NodeSource @NodeSource]

Is Express 5 actually faster? 📉

Fresh benchmarks show Express v5 running ~10% slower than v4 on middleware-heavy routes across all Node.js versions.

While Express 5 brings great API improvements, the performance overhead in the new router is real. Is the migration a priority for your high-throughput services? 🧐

#NodeJS #ExpressJS #Backend #WebDev

[NodeSource @NodeSource]

Steady start to the week for the Node.js ecosystem 🟢

The deprecation of `sqlite3` isn’t a panic moment—it’s evolution. Most teams are moving to `better-sqlite3` for production: it’s faster, sync-first, and battle-tested.

`node:sqlite` is an exciting native alternative, but keep in mind it’s still in active development (experimental).

Are you migrating now, or waiting for the native module to stabilize? 🛠️

#NodeJS #WebDev #Backend #JavaScript

[NodeSource @NodeSource]

Handling massive datasets or paginated APIs in Node.js often turns into a memory management game. 🧠

When you're pulling unbounded data (DB cursors, streams, infinite APIs), what is your go-to pattern for keeping the event loop happy?

⬇️ Context in the thread

[NodeSource @NodeSource]

🚀 Express.js is entering a new era

After years of stability (and stagnation), the world’s most popular Node.js framework is being modernized, with new governance, better performance, and collaboration.

Here’s what’s next for Express 6 and beyond 👇
https://t.co/2Sexy5AuqW

[NodeSource @NodeSource]

✨Highlights from JSConf North America 2025✨

Last week’s JSConf NA brought together maintainers, contributors, and companies shaping the future of JavaScript, and it was an unforgettable week for NodeSource and the open-source ecosystem.

Check it out: https://t.co/sXdZ7InW1K