tooling

This is a discussion hub for people who build developer tools using Node.js—think linters, test runners, build systems, package managers, and similar utilities. The group exists to figure out what Node.js could do better to make it easier to write these kinds of tools.

It's not a place to find finished tools or internal Node.js infrastructure. Instead, it's where developers gather to share what's working well, what's frustrating, and what features or improvements Node.js itself could offer. For example, if you're building a linter or bundler in Node.js and you keep running into the same limitation, this is where you'd raise that problem and talk with others who've hit the same wall.

The group operates informally on a public Slack channel and through GitHub discussions and meetings. Anyone can join the Slack workspace, share their experience building tools, propose ideas, or help document what the community learns. The README acknowledges the whole thing is still being figured out, so there's room for input on how it should work.

This would appeal to anyone making developer tools—whether you're building a new test framework, a bundler, a linter, or a code compiler. It's also relevant to maintainers of existing tools who want to influence what Node.js offers to make their work easier. The real value is in pooling feedback from tool developers so the Node.js project can prioritize improvements that actually matter to the people using it for this work.