You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If I do npm run build on SvelteKit next.119, and then try to start the app with node build, I get the following error:
file://.../app/build/index.js:2502
serverFetch: hooks.serverFetch || fetch
^
ReferenceError: fetch is not defined
at get_hooks (file://.../app/build/index.js:2502:37)
at init (file://.../app/build/index.js:2207:12)
at file://.../app/build/index.js:2554:1
at ModuleJob.run (node:internal/modules/esm/module_job:175:25)
at async Loader.import (node:internal/modules/esm/loader:178:24)
at async Object.loadESM (node:internal/process/esm_loader:68:5)
at async handleMainPromise (node:internal/modules/run_main:63:12)
I know that everything worked fine in next.117. This seems to be related to the serverFetch patch. I'm not aware of anything unusual in my code that should have caused it to break. In any case, the error suggests the issue is with SvelteKit itself.
Describe the bug
If I do
npm run build
on SvelteKit next.119, and then try to start the app withnode build
, I get the following error:I know that everything worked fine in next.117. This seems to be related to the serverFetch patch. I'm not aware of anything unusual in my code that should have caused it to break. In any case, the error suggests the issue is with SvelteKit itself.
Information about your SvelteKit Installation:
Severity
Highest. This makes it impossible for me to use SvelteKit on next.119.
The text was updated successfully, but these errors were encountered: