-
Notifications
You must be signed in to change notification settings - Fork 19
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
support getLoadContext
when using Vite
#115
Comments
Did you have a particular use case that you need it for? See #92 for a previous time when this was brought up. |
I'm migrating an existing codebase (~80 routes) and they are all setup to pull resources (like database client, environment variables) from the loader context. We did this, in theory, to make our app more portable across all runtimes/environments. Ironically, its now the only thing preventing us from using vercel. |
If you could show me where this change would live... I'd be happy to send you a PR. |
Same situation here, very desperate |
Same issue here, we have shared context, and currently we need to make multiple API calls per session to retrieve that context (config related). |
@TooTallNate any plans on supporting Hydrogen Vite? I know that |
getLoadContext
function so that the all loaders can get that context.I don't care how it's implemented, I just need to be able to define my loader context somewhere and use it in a vercel app.
The text was updated successfully, but these errors were encountered: