test: add remote file test

[ThornWalli]

Hello :)

have an addition here for the test, there is still missing the retrieval of an external resource.

The whole thing has now but a background ;) we use in our package nuxt-speedkit the @nuxt/image and can not update here for a long time basics/nuxt-booster#521.

This all came with the ipx update to ohmyfetch with the included node-fetch@3.

Could find two problems:

1. node-fetch update to version 3 brings errors when calling many requests.

This topic can be found here:
- node-fetch/node-fetch#1474
- node-fetch/node-fetch#1325

And can be easily reproduced with the many call to http://localhost:3000/width_200/https://avatars.githubusercontent.com/u/23360933?s=500 in dev mode.

2. Another problem I encountered is in the test.
   There I get this error message when running ohmyfetch.fetch and in worst case a segment fault jest.

Error Message	Segment Fault

I created a small repo for ohmyfetch, in the test you can see that the call has a problem.

Therefore, this test will probably not be passed in PR.

Could I run it completely if I replaced ohmyfetch with node-fetchor changed the import to:

import { fetch } from 'ohmyfetch/dist/node.mjs'

In both cases, I had to extend the jest configuration with babel, because node-fetch@3 runs in jest only as ESM (node-fetch/node-fetch#1289) and the node.mjs has to be converted as well.

Now I'm asking myself, what's the next step here?

1. wait for a node-fetch@3 update, where one of the given PRs is included.
2. the use of ohmyfetch in the jest must work. (rollup issue?)

The easiest solution would be to switch back from ohmyfetch to node-fetch@2.

Thanks already for the help :)

unjs/ofetch#57

[pi0]

Thanks for working on this PR and sorry for inconveniences you had with node-fetch versioning. You weren't alone. The latest nuxt is using unjs/node-fetch-native to address most of the problems you had.

[ThornWalli]

@pi0 I have seen that it is now installed, could you update the dependency node-fetch in node-fetch-native?

Have warnings with MaxListeners, which should then be fixed.

[pi0]

Sure! You can always make issue in the repos this way I can find it faster.