Seattle, WA, USA
2014
  |  By Estefany Aguilar
Debugging has always been part of the craft. But in today’s systems — distributed, asynchronous, and increasingly opaque — debugging is no longer just difficult. It’s fragmented. Despite better tooling, more telemetry, and the rise of AI-assisted workflows, many developers still experience the same core frustrations when trying to understand what’s actually happening in production.
  |  By Estefany Aguilar
If you’ve ever debugged a Node.js application in production, you’ve likely seen this: Sourcemaps were supposed to solve this. And technically, they do. But in practice, most teams still struggle to make sourcemaps available when they’re actually needed.
  |  By Estefany Aguilar
If you’ve worked with Node.js in production, you already know that streams are not a niche feature. They are part of the foundation. They power how data moves through systems, how I/O is handled, and ultimately, how applications scale. For years, that foundation has held up remarkably well. At the same time, many developers—junior and senior alike—have shared a similar feeling: while streams are powerful, they don’t always feel natural to work with.
  |  By NodeSource
On March 31, 2026, security researcher Chaofan Shou noticed something odd: the complete source code of Claude Code — Anthropic's flagship AI coding CLI — was sitting in plain sight on the public npm registry. 512,000 lines of TypeScript. 59.8 MB of source maps. Everything. The irony? The code contains an "Undercover Mode" specifically built to prevent internal Anthropic secrets from leaking into public commits. They built a secrecy subsystem, then accidentally published everything.
  |  By Estefany Aguilar
In today’s ecosystem, building with Node.js is not just about writing code. It’s about running systems that are reliable, secure, and able to evolve over time. That’s where collaboration at the foundation level becomes critical. At NodeSource, working closely with the OpenJS Foundation is not just a partnership. It’s a commitment to the long-term health, security, and evolution of the Node.js ecosystem.
  |  By Estefany Aguilar
There’s something powerful about stepping away from your day-to-day work and being surrounded by people asking the same questions you’ve been thinking about: At JSConf Spain, those answers don’t come from a single talk. They emerge from patterns — ideas that repeat across different speakers, different companies, and different perspectives.
  |  By Adrián Estrada
Today marks a critical step forward for enterprise Node.js. In partnership with the OpenJS Foundation, NodeSource is launching a Node.js LTS Upgrade & Modernization program to provide companies with a secure and streamlined path to migrate business-critical applications off legacy and End-of-Life (EOL) Node.js versions and onto the latest Long-Term Support (LTS) releases.
  |  By Estefany Aguilar
February was not defined by major feature drops. It was defined by process hardening, structured release cadence, and continued runtime iteration across both LTS and Current lines. For production teams, this month reinforced three pillars: This is the technical breakdown of what actually mattered.
  |  By Estefany Aguilar
Your service doesn’t crash. It just gets slower. Latency creeps up. Requests that used to take 20ms now take 120ms. p99 drifts. Throughput drops slightly. Nothing is obviously broken — but the system feels congested. You open your dashboards. And yet, something is clearly off. In many production systems, this is what Event Loop pressure looks like. Not a failure. Not an outage. But a runtime that is struggling to make forward progress. The JavaScript thread is not dead. It’s busy.
  |  By Estefany Aguilar
You’ve probably heard: “Node.js is single-threaded.” That statement is only partially correct. The JavaScript engine (V8) is single-threaded. Node.js as a runtime is not. Under the hood, Node.js uses multiple threads — through libuv and the operating system — to handle I/O and computationally expensive work. So the real question isn’t whether Node.js is single-threaded. It’s.
  |  By NodeSource
If you are installing Node.js in Linux to use it in production, there is a big chance that you are using NodeSource Node.js Binary Distributions. In this talk you can find the process in which NodeSource Node.js Binary Distributions is updated, how new versions are supported, the human and infrastructure process, and some limitations of maintaining the channel. Also and most importantly, how the community can get involved with this project.
  |  By NodeSource
Node.js v14 has just been released. It comes with exciting features and enhancements. More importantly, it will be promoted to Long-Term Support (LTS) in October. The time to start trying said features and start testing your applications and secure a smooth transition is now. In this talk we will be showing the most relevant of these new features implementation examples and more.
  |  By NodeSource
NodeSource’s Enterprise Node.js (NSolid), combines the performance and open-source ecosystem of Node, with the first secure, end-to-end solution for scaled production diagnostics and monitoring that doesn’t incur latency overhead.
  |  By NodeSource
NodeSource developed a GitHub Action that can be used as a lightweight CI workflow. Whenever a PR is submitted, NodeSource's 'Node Certified Modules' (NCM) uses the NCM pipeline to check and evaluate the project. The PR then fails or passes depending on the project’s risk profile. The integration delivers detailed code annotations to reflect where certain risk factors occurred in your project.
  |  By NodeSource

Amazon Web Services, the “Powered by AWS” logo, and AWS Lambda are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.

  |  By NodeSource

Amazon Web Services, the “Powered by AWS” logo, and AWS Lambda are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries.

  |  By NodeSource
Heap snapshots are one of the first steps to take when debugging Node.js applications with poor performance. N|Solid can help by automatically triggering heap snapshots of your Node.js applications and services in production, when they're under real-world load.
  |  By NodeSource
Node.js's popularity can be attributed to its ease of adoption with JavaScript developers, a lightweight and performant core, and suitability for applications across platforms. In this guide, we will look specifically at six Node.js web frameworks.
  |  By NodeSource
Analysts Jeffrey Hammond, Diego Lo Giudice, and Christopher Condo explain in this Forrester report why digital and software development leaders should take a customer-focused approach to software development to support digital transformation. Organizations often think of modernization in terms of technology choices-and as NodeSource has seen firsthand, Node.js is a key part of the tool set for application modernization. However, this report indicates that most IT organizations don't have the right operational models to develop and deliver great digital experiences.
  |  By NodeSource
Analysts Jeffrey S. Hammond and John R. Rymer explain in this Forrester report how serverless - a set of cloud services, programming patterns, business models, and design ideas - enables new levels of flexibility in software through applications that respond to events.
  |  By NodeSource
While startups rarely enjoy the resources of a large organization, they usually enjoy a comparative "easy-mode" when it comes to technology adoption. Once a company has reached a certain size, or has existed for long enough, technical debt builds up, organizational ossification sets in, and bureaucratic creep becomes pervasive. This white paper covers our findings from over the last four years of engaging deeply with our enterprise customers: advising, training, and supporting them with our products and expertise through their Node.js adoption journeys.
  |  By NodeSource
PayPal, Netflix, and Walmart show the way to achieve rapid digital transformation of legacy systems. Modernizing systems and processes has become a top priority for businesses across all verticals. Organizations are looking for the fastest and most effective route to modernization; Node.js is emerging as the de facto choice for companies looking to build the apps and other infrastructure needed to make such a move.
  |  By NodeSource
You've written the next great application, in Node-and you're ready to unleash it upon the world! Which means you can no longer run it on your laptop, you're going to actually have to put it up on some server somewhere and connect it to the real Internet. There has probably never been a better or easier time to learn basic Linux system administration. This tutorial will take you through the steps to deploy and run your application on a Linux server using systemd, which is the replacement to init and upstart in older Linux systems.

NodeSource empowers organizations to successfully design, build, and manage Node.js applications and compete in the modern digital era.

The NodeSource product suite is built around the N|Solid runtime, a drop-in replacement for the Node.js runtime that offers low-impact performance monitoring and enhanced security. Alone or alongside our Professional Services and Support offerings, the NodeSource platform helps to mitigate security risk and provide deep operational visibility into mission-critical applications.

The N|Solid platform delivers enhanced security and unparalleled visibility into application performance and health. Customizable security policies and real-time vulnerability scanning of third-party JavaScript modules running in production help protect code against malicious attacks. Detailed application metrics help teams identify issues sooner, reduce time to resolution, deliver peak performance, and keep infrastructure costs under control.

Why N|Solid?

  • Faster Time to Resolution: The most advanced Node.js monitoring and diagnostic tools to help identify and tackle tricky issues.
  • Stronger Infrastructure: Deep performance insights help you build highly reliable applications and minimize infrastructure costs.
  • Hardened Security: Mitigate unseen security risks with custom security policies and real-time vulnerability scanning.