Warn when non sveltekit fetch method called in load function

[GoodBoyNinja]

Describe the problem

I just spent a few hours debugging a page.server route that worked perfectly fine in local dev but threw an error in production, the route used fetch to get data from an api route, it turns out I forgot to deconstruct the fetch function from the load arguments and accidentally used the global one.

It’s such a small nuance that’s easy to miss and since the code only breaks in production it feels impossible to debug especially on a large repo, typescript doesn’t have any problems with the code since fetch is available globally.

I know that if there was a warning that the fetch function I am using is not the sveltekit one I would fix it in a few seconds rather than hours, so I imagine that if it’s possible to add one, it could be beneficial to other people too.

Describe the proposed solution

“Warning: use sveltekit’s fetch function inside a load function [link to docs]”

Alternatives considered

Dying

Importance

would make my life easier

Additional Information

No response

[Conduitry]

There are valid use cases for calling the global fetch in a +page.server.js file. The event.fetch passed as an argument is only really needed if you want to pass along cookies from the user's request, or do any of these other things.

There are warning when using the global fetch instead of the fetch passed to universal load functions called on the browser, but I'm not sure it makes sense to have a warning during server load functions, where it is perfectly valid to use the global fetch.