-
-
Notifications
You must be signed in to change notification settings - Fork 263
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(vite-plugin-nitro): provide req and res to renderer #806
feat(vite-plugin-nitro): provide req and res to renderer #806
Conversation
PR adds full req and res object from h3 to the analog event handler for app rendering closes analogjs#802
✅ Deploy Preview for analog-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-app ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for analog-blog ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
packages/vite-plugin-nitro/src/lib/plugins/dev-server-plugin.ts
Outdated
Show resolved
Hide resolved
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.
🍪
Looks great @Jefftopia! One small cleanup item on the interceptor naming |
Thanks! @allcontributors add @Jefftopia for code |
I've put up a pull request to add @Jefftopia! 🎉 |
PR adds full req and res object from h3 to the analog event handler for app rendering
closes #802
closes #586
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Which package are you modifying?
What is the current behavior?
Current behavior is that the full, raw request and response are not provided to Analog, which limits the ability to use cookies from the incoming request.
Closes #802
What is the new behavior?
Now both the runtime renderer event handler and the nitro dev server have access to the request and response, which can then be provided to the application.
Does this PR introduce a breaking change?
Other information
[optional] What gif best describes this PR or how it makes you feel?