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

Code breaks on deploy to vercel #45

Closed
1 task done
Complexlity opened this issue Mar 1, 2024 · 2 comments
Closed
1 task done

Code breaks on deploy to vercel #45

Complexlity opened this issue Mar 1, 2024 · 2 comments

Comments

@Complexlity
Copy link
Contributor

Describe the bug

I have defined a new route on "/" while the frame is on "/api". I want the "/" to render normal HTML while leaving the "/api" route to render the frame.

This works locally and on stackblitz but does not work when I deploy to vercel. It fails in two ways:

  1. The "/" route returns "not-found" when I try to get on the browser. The get('/') path apparently doesn't get built
  2. The imported jsx is not built so it is unable to find the "../images/welcome.jsx

Both work locally but when deployed on vercel, it breaks

Link to Minimal Reproducible Example

https://stackblitz.com/~/github.com/Complexlity/frog-init

Steps To Reproduce

No response

Frog Version

0.21.0

TypeScript Version

No response

Check existing issues

Anything else?

No response

@Complexlity
Copy link
Contributor Author

Issue 2 is similar to this: #30

@jxom
Copy link
Member

jxom commented Mar 1, 2024

Yeah, unfortunately these are both Vercel Functions limitations:

  1. Vercel Functions can only reside under the /api route
  2. Vercel Functions cannot import JSX files by default (we are looking into a workaround for this as per Importing files doesn't work on Vercel deployment #30)

@jxom jxom closed this as not planned Won't fix, can't repro, duplicate, stale Mar 1, 2024
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

No branches or pull requests

2 participants