Become a sponsor to Nock
nock
is the most widely used http mocking library for Node.js. It's first commit by @pgte is from September 2011. Around 6 years later, Pedro invited @gr2m as a maintainer, about a year after Pedro was no longer able to maintain nock
himself.
Over time, a new maintainers team took on nock
, with the goal to make the project easier to maintain and to contribute to. Most notably, we achieved 100% test coverage, setup automated releases, triaged all open issues and pull requests, and started to document the vast code base that grew organically over a decade..
nock
is a huge monolith of intertwined logic which is hard to understand and impossible to maintain with a few hours of time that people graciously donated by its maintainers and contributors from time to time.
In order to make nock
's code base easier to understand, to maintain, and to make it possible to distribute the maintainership across more people, we decided the code base needs to be split up into separate modules
@nock/intercept
- overwrite Node's native APIs to hook into the request lifecycle.@nock/mock
- provides API to define HTTP mocks@nock/recorder
- APIs to record requests/responses and replay them from files
We decided to use $3,000 of a past sponsorship to start off this work with a focused effort by @gr2m, but it will not be enough. You can follow along on the process at https://github.com/nock/nock/discussions/2247
Meet the team
-
Gregor Martynus gr2mMaintainer of @nock, @semantic-release, @Probot, @Octoherd, and @all-contributors, among many smaller projects
-
Richard Littauer RichardLittMaintainer of lists, coder of birdwatching tools.
-
Paul Melnikow paulmelnikowDev–product hybrid
-
Matt R. Wilson mastermattWho let this guy in?
$5 a month
SelectThis tier is for individual people only.
By sponsoring nock
you become a contributor, just as important as contributors to documentation, code, or supporting other users with their questions.
Thank you 💖
$100 a month
SelectThis tier is for organizations. If you depend on nock
, you have a vested interest that bugs and security concerns are addressed quickly, that the code base is modern and performant, and that the project adapts to new requirements and technologies.