The overhead of managing the complexity of jest in this case is unnecessary. We can simplify our dependency management and test tooling by just using the NodeJS test runner.
- We'll need to consider what this means relative to the versions of NodeJS we execute our tests against (the test runner has improved/changes over Node versions 18/20/22)
- Consideration for browser
fetch API is really the only thing that is required I think.
The overhead of managing the complexity of jest in this case is unnecessary. We can simplify our dependency management and test tooling by just using the NodeJS test runner.
fetchAPI is really the only thing that is required I think.