Rhys Evans

cheers john - great fix for a bug that's been frustrating me all morning

Maybe another possible fix (when jQuery is present) would be to have something like the following if(!evData.raphIgnore) { this.toFront(); $(this.node).trigger("mouseenter", {raphIgnore: true}); } ... but then you'd need to use...

node-fetch@3 is ES modules only, so it would require updating this entire library from commonjs. Probably something I'll look at after addressing the ling backlog of other issues

I think this is expected behaviour, though I agree it's not obvious and not documented very well. To get more transparent behaviour it's best to name your routes ```js it('foo',...

Suggested API - `.spy(matcher, transparent)` - transparent is Bool

See official advice from nodejs https://nodejs.org/dist/latest-v12.x/docs/api/esm.html#esm_dual_commonjs_es_module_packages

@trixn86 this is partly inspired by your issue on fetch-mock-jest. I'm interested on feedback

- [x] Define a new Route class that encapsulates all properties of a route - [ ] Provide some way of getting a reference to the instances of Route while...

Cheers for the tip off - I'll start running tests against node-fetch 3 and hopefully resolve it

Have you raised this on ky-universal? IMHO it's a really bad idea for them to bundle a beta of node-fetch. But I see what the problem is. fetch-mock declares a...