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

Endpoints 404 with vercel #293

Closed
Mozzesdev opened this issue Jul 3, 2024 · 2 comments · Fixed by #295
Closed

Endpoints 404 with vercel #293

Mozzesdev opened this issue Jul 3, 2024 · 2 comments · Fixed by #295
Assignees
Labels
bug Something isn't working

Comments

@Mozzesdev
Copy link

Mozzesdev commented Jul 3, 2024

Describe the bug
I use an express app to have the api on the server itself it returns a 404, it's like it doesn't find the path with vercel

To Reproduce
Just use this preset or whatever with vercel and express and check the deploy, looks great but the other endpoints are dead
pnpm create @batijs/app --react --tailwindcss --telefunc --express --vercel --eslint

Expected behavior
The other endponts other than "*" returns will return 202 or whatever if it defined in the server

Screenshots
image
image

@Mozzesdev Mozzesdev added the bug Something isn't working label Jul 3, 2024
@magne4000
Copy link
Member

magne4000 commented Jul 3, 2024

The Vercel integration is indeed incomplete, it seems like when I'm choosing a server it is used locally but not by Vercel.

I should have a fix by tomorrow.

@magne4000
Copy link
Member

magne4000 commented Jul 4, 2024

I released a 0.0.217-beta.1 version that should fix the issue.
You can try it with pnpm create @batijs/app@beta ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants