fech function is not working in production mode

[ldcastanheira]

Hello everyone,

I am new in svelte also in trying to deploy to vercel. So I do not know why this function works perfectly in development environment but does not work in production (vercel). Could you help me?

async function doPost(message: string) {
    const res = await fetch('https://xxxx.bxxxxwhats.com/send-message', {
        method: 'POST',
        headers: {
            'Content-Type': 'application/json'
        },
        body: JSON.stringify({
            jid: "555xxxxxxxxxxx",
            message: message,
            token: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        })
    })

const json = await res.json()
return JSON.stringify(json)

}

Please let me know if you need more information or this is enough.

Thanks a lot!!!

[isaiahscheel]

I'm running into the same. I thought it was due to Vercel's recent outage https://www.vercel-status.com/incidents/ndnw1mxqjkh8 but they say it is resolved and I am still running into issues.

Getting stuff in my logs like:

TypeError: Failed to parse URL from [object Request]
at Object.fetch (node:internal/deps/undici/undici:11576:11)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.fetch (file:///var/task/.svelte-kit/output/server/index.js:2239:12)
at async Promise.all (index 0)
at async load (file:///var/task/.svelte-kit/output/server/entries/pages/_page.server.js:194:98)
at async load_server_data (file:///var/task/.svelte-kit/output/server/index.js:582:18)
at async file:///var/task/.svelte-kit/output/server/index.js:1945:18 {
[cause]: TypeError [ERR_INVALID_URL]: Invalid URL
at new NodeError (node:internal/errors:405:5)
at new URL (node:internal/url:637:13)
at new Request (node:internal/deps/undici/undici:7132:25)
at fetch2 (node:internal/deps/undici/undici:10715:25)
at Object.fetch (node:internal/deps/undici/undici:11574:18)
at fetch (node:internal/process/pre_execution:242:25)
at n (/var/task/___vc/__launcher/__launcher.js:14:5526)
at fetch (file:///var/task/.svelte-kit/output/server/index.js:2261:18)
at #options.hooks.handleFetch (file:///var/task/.svelte-kit/output/server/index.js:2778:79)
at Object.fetch (file:///var/task/.svelte-kit/output/server/index.js:2239:33) {
input: '[object Request]',
code: 'ERR_INVALID_URL'
}
}

and

TypeError: (intermediate value) is not iterable
    at load (file:///var/task/.svelte-kit/output/server/entries/pages/_page.server.js:195:98)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async load_server_data (file:///var/task/.svelte-kit/output/server/index.js:582:18)
    at async file:///var/task/.svelte-kit/output/server/index.js:1945:18

and lastly a custom one that is catching where I fetch the data in my load function

Failed to fetch or parse data. Failed to parse URL from [object Request]

[isaiahscheel]

Yeah seems to be a load function with a fetch. I did make a Vercel issue here in the discussion: https://github.com/orgs/vercel/discussions/4600 but you did a lot more leg work with getting that repo set up and the test site so that hopefully will give them some more evidence than my hand wavey complaining!

[kylepulman]

Same issue here, y'all. To confirm my suspicions that it's a Vercel issue, I tried @bent101's code on Render (with the node server adapter) and it's working just fine.

[isaiahscheel]

Does no one but us fetch in load functions and use Vercel? Thought that was pretty standard practice! Oh well, hopefully they can solve it sooner than later.

[stefanpullen]

Same issue on my side. Hope they will resolve it soon. Spent the last three hours debugging in vain.

[johannesmutter]

Same issue. Temporary fix: use node-fetch instead of SvelteKits fetch:
https://github.com/orgs/vercel/discussions/4600#discussioncomment-7381011

[dummdidumm]

Looks like an upstream issue: #10918 (comment)