Rhys Evans

I'm seeing that repl.it is installing peerDependencies, which forces the use of [email protected]. When I install and run the same code locally it does not install the peerDependencies. It looks...

Final proposal: ```js fetchMock .mock(matcherFunc, 200) .mock(matcherFunc2, 200).$mock2 fetchMock.called('mock2') // gets the calls actually handled by matcherFunc fetchMock.called(matcherFunc2) // gets the calls that matcherFunc matches ``` With the easier naming...

Or possibly ```js fetchMock.mock(matcher, response, name) ``` duck-typing ```js fetchMock.mock(object, name) // expect object to have a response property ```

`absPath:` = absolutePath....? `page:` ?

Sorry for the slow response (no pun intended) - completely missed this message. `lastResponse()` etc. works as an API for me. I guess where it gets tricky is in knowing...

The current implementation would still be supported (under the hood the options all get smooshed together anyway), but I see the API more as - parameter 1 - decide which...

mocha puppeter https://www.google.com/search?q=puppeteer+mocha&oq=puppeteer+mocha&aqs=chrome..69i57j0l4.3296j1j7&sourceid=chrome&ie=UTF-8

playwright mocha https://playwright.dev/#version=v1.0.1&path=docs%2Ftest-runners.md&q=mocha https://medium.com/@arjunattam/fast-and-reliable-cross-browser-testing-with-playwright-155c0e8a821f

Feel free to write some based on what you've learned/assumed from your PR. I don't have the time to author some myself at the moment

This also has implications for overwriteRoutes - I think the current implementation should probably be ditched - retrieving of matched calls should rely far less on [coercively] named handlers -...