-
Notifications
You must be signed in to change notification settings - Fork 313
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
feat: h3 adapter #358
feat: h3 adapter #358
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
894b590
to
598f395
Compare
Co-authored-by: Daniel Roe <[email protected]>
Co-authored-by: juliusmarminge <[email protected]>
Co-authored-by: Daniel Roe <[email protected]>
Co-authored-by: Daniel Roe <[email protected]>
Co-authored-by: Daniel Roe <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reminder for myself to look over these types, doesn't make sense having to add an any generic in a bunch of places like this...
Generic adapter that can be used for Nitro (new SolidStart, Nuxt etc) and other servers using H3
Bored of setting up react vite frontend. Example works with any of the vite clients from the express or fastify examples. We are probably good with just a single one that connects to either of the backend adapter examples