Any reason to strip response body when no-cors mode is provided to fetch?

[raythurnvoid]

I'm using the svelte-kit's provided fetch method and calling the Microsoft token API to get a new token and call the ms-graph API; in my current configuration, I have to perform the request from Node; Microsoft checks the Origin header and will respond with an error if set. I've tried to provide fetch with mode: 'no-cors' and I've noticed that the response body is stripped away:

kit/packages/kit/src/runtime/server/fetch.js

Line 68 in ab5f1c1

if (mode === 'no-cors') {

Is there any reason to remove the body response when no-cors is being used?

[Rich-Harris]

Is this happening in a fetch from a shared load function (+page.js) or a server-only one (+page.server.js)? If the first, this is intentional — the behaviour needs to be consistent between browser and server. If the second, you may have found a bug — please open an issue!

[raythurnvoid]

Actually, it's happening in the +server.js module, i'm using the fetch provided in event: RequestEvent

at the moment, I worked around it by using the global fetch provided by node.