Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/api routes doesn't work !! #2205

Closed
potros opened this issue Aug 14, 2021 · 3 comments · Fixed by #2206
Closed

/api routes doesn't work !! #2205

potros opened this issue Aug 14, 2021 · 3 comments · Fixed by #2206

Comments

@potros
Copy link

potros commented Aug 14, 2021

Describe the bug

when i add a /api route it doesn't work and tells me that there is no /api route

Reproduction

add a /api route in the routes folder and try to access it in the browser

Logs

vite] connecting...
client.ts:52 [vite] connected.
index.mjs:1976 <Error> received an unexpected slot "default".
validate_slots @ index.mjs:1976
api:1 Failed to load resource: the server responded with a status of 404 (Not Found)

System Info

System:
    OS: Windows 10 10.0.18363
    CPU: (4) x64 AMD A10 PRO-7800B R7, 12 Compute Cores 4C+8G
    Memory: 6.94 GB / 9.92 GB
  Binaries:
    Node: 16.6.2 - C:\Program Files\nodejs\node.EXE
    npm: 7.20.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 92.0.4515.131
    Edge: Spartan (44.18362.387.0)
    Internet Explorer: 11.0.18362.1
  npmPackages:
    @sveltejs/kit: next => 1.0.0-next.147
    svelte: ^3.34.0 => 3.42.1

Severity

blocking all usage of SvelteKit

Additional Information

No response

@ignatiusmb
Copy link
Member

You might be running into #2046, have you tried restarting the dev server?

@potros
Copy link
Author

potros commented Aug 14, 2021

yes , but didn't solve the problem

@Conduitry
Copy link
Member

We need a full, minimal reproduction that we can clone that demonstrates the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants