mv-go

Having the same issue here and can confirm that switching back to Node 16 helped. However I decided to follow the workaround proposed by @KrisCarr and used `http-get://127.0.0.1:9000` with Node...

Would be nice to have this fixed. Thanks to MrSimonEmms for a PR :)

Hey! Will try today, yup.

hey @IlCallo , sorry for a late reply! Unfortunately, I was not able to reproduce the issue on a fresh install. Which only has me bugging, what is going wrong...

Ooops, never mind, I think I found it. What helped is removing a bunch of (I think) unnecessary code from my project's `vue.config`. Yeah, we do have a fairly large...

ATM I'm working around this by explicitly returning `null` in the `keyFunction` where necessary, however it'd be great to be able to return `null || undefined` as documentation states

Yes, I agree - this could be a breaking change. Speaking of which, I would consider switching the behaviour from `falsy` to strictly `null || undefined`. Consider the following case:...

> In JavaScript, `0` is considered a falsy value. [Source](https://developer.mozilla.org/en-US/docs/Glossary/Falsy) I understand, yes. So in my example above you would suggest that `fetch` should not be triggered when `id` is...

Is this a desired behaviour? It would seem common to have an object on the backend with an `id = 0`

Fair enough. Should we consider implementing changes regarding my initial message in this issue - to include `undefined` in typings. Or shall we just close this one as irrelevant? :)