-
Notifications
You must be signed in to change notification settings - Fork 57
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
hyperdrive is not included in the runtime instance #279
Comments
Indeed we don't generate it for now: Lines 43 to 58 in 33612ee
The feature for local development in wrangler was released 4 days ago: cloudflare/workers-sdk#6612 I will have a look this week to fix this |
Hey @atinux cool, thank you, but there seem to be another issue actually, and why hyperdrive does not show up in runtime. The problem seem to be https://developers.cloudflare.com/hyperdrive/configuration/connect-to-postgres/
I'm not sure where to go from where, any idea? |
This is how you can enable it: export default defineNuxtConfig({
hub: {
bindings: {
compatibilityFlags: 'nodejs_compat_v2'
}
}
}) |
Doesn't seem to set it/change it. By any chance if this is set manually through cloudflare, it wont let nuxt overwrite the config, maybe? |
Describe the bug
I've setup cloudflare hyperdrive correctly in the
nuxt.config.ts
in bindings; I noticed that inwrangler.toml
it does not generate the bindings, but maybe this is due to to not working locally.I tested in on remote, and in the logs
POSTGRES
env does not show up; and theprocess.env.POSTGRES
returns null, I've also logged :event.context.cloudflare.env
which returns all other bindings, and env variables, but there's noPOSTGRES
env variable that binds to hyperdrive.Steps to reproduce
hub.bindings.hyperdrive
process.env.POSTGRES
orevent.context.cloudflare.env
hyperdrive
Expected behavior
POSTGRES
should havehyperdrive bindings
The text was updated successfully, but these errors were encountered: