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
{{ message }}
Repository navigation
Error after initial start of the application (404 Not Found) #18
npx degit houdinigraphql/intro hello-houdini
cd hello-houdini
npm i
npm run dev
node -v (v18.16.0)
open http://localhost:5173/
Error: Not found: /
at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:394:13)
at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:243:5)
at #options.hooks.handle (/node_modules/@sveltejs/kit/src/runtime/server/index.js:41:55)
at Module.respond (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:240:40)
Error: Not found: /
at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:394:13)
at resolve (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:243:5)
at #options.hooks.handle (/node_modules/@sveltejs/kit/src/runtime/server/index.js:41:55)
at Module.respond (/node_modules/@sveltejs/kit/src/runtime/server/respond.js:240:40)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Ah, didn't chech that should use the final branch. That one gives me more detailed error:
SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON
at JSON.parse (<anonymous>)
at Proxy.eval (/node_modules/@sveltejs/kit/src/runtime/server/page/load_data.js:286:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async eval (/@fs/C:/git/course/houdini-pokemon-final/$houdini/runtime/client/plugins/fetch.js:62:12)
at async network (/@fs/C:/git/course/houdini-pokemon-final/$houdini/runtime/client/plugins/fetch.js:23:24)
Activity
kasparpalgi commentedon Oct 21, 2023
500 Internal Error for me at http://localhost:5173/6
kasparpalgi commentedon Oct 21, 2023
Ah, didn't chech that should use the final branch. That one gives me more detailed error:
kasparpalgi commentedon Oct 22, 2023
I suspect it was API issue. As I don't know the test API used, I just connected to my Hasura GraphQL API endpoint and worked well.