next-10
March 4, 2026 · View on GitHub
The purpose of this repository is to work collaboratively on the strategic directions for the next 10 years of Node.js (Building on the successful first 10).
For more context see: https://github.com/nodejs/TSC/issues/797
We meet every other week and an issue with the agenda for the meeting will be opened in the repo a few days
in advance. You can find the dates/times for future meetings on the Node.js calendar labeled as Node.js Next 10 years.
Team members
- @BethGriggs - Bethany Nicolle Griggs
- @bmeck - Bradley Farias
- @bnb - Tierney Cyren
- @darcyclarke - Darcy Clarke
- @dominykas - Dominykas Blyžė
- @joesepi - Joe Sepi
- @legendecas - legendecas
- @ljharb - Jordan Harband
- @ovflowd - Claudio Wunder
- @Qard - Stephen Belanger
- @ruyadorno - Ruy Adorno
- @sheplu - Jean Burellier
- @nomadtechie - Amal Hussein
- @marco-ippolito - Marco Ippolito
- @UlisesGascon - Ulises Gascón
- @JakobJingleheimer - Jacob Smith
Emeritus
- @ahmadawais - Ahmad Awais ⚡️
- @andrewhughes101 - Andrew Hughes
- @bengl - Bryan English
- @BridgeAR - Ruben Bridgewater
- @designMoreWeb - Divy Tolia
- @devsnek - devsnek
- @F3n67u - Feng Yu
- @ghinks - Glenn
- @iansu - Ian Sutherland
- @jasnell - James M Snell
- @keywordnew - Manil Chowdhury
- @mcollina - Matteo Collina
- @mhdawson - Michael Dawson
- @mmarchini - mmarchini
- @MylesBorins - Myles Borins
- @puzpuzpuz - Andrey Pechkurov
- @richardlau - Richard Lau
- @ronag - Robert Nagy
- @targos - Michaël Zasso
- @tniessen - Tobias Nießen
- @trivikr - Trivikram Kamat
- @wesleytodd - Wes Todd