Wrangler Local Dev Broken
Ah, 3.84.1 works locally? Does it cooperate with local dev against a remote connection string?
12 Replies
Moving this to a thread so I can keep things straight
3.84.1 works with localhost db
but with remote neon db it does show
Even if my connectionString is
WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_DB="postgresql://repguide_owner:[email protected]/repguide?sslmode=require"
So it doesn't take sslmode
I set into considerationNo,
workerd
interpolates. I wonder if this is the workerd change, then.Correction, 3.85.0 also works, but only with localhost
So it seems like > 3.86.0 breaks
Okay so my guess
<= 3.85.0 only works with
localhost
connectionString
>= 3.86.0 doesn't work with any connectionString -> timeoutsCan confirm 3.85.0 works locally for me as well
I've messaged the team, and we'll take a look. Thank you.
Thanks for taking a look so quick. And glad to hear that the intended behavior is, that even remote connection strings should be supported, so we can use solutions like Neon for development š
Definitely, we want you to be able to use remote db's for dev, we added this a few versions ago
@alex (he/him) @Slylencer while we investigate local dev, just making sure you're unblocked since npx wrangler dev --remote is working
For me not really. We have an architecture with multiple workers connected with service bindings to use RPC calls, that doesn't seem to work if we use
--remote
, since it doesn't find the scripts anymoreI'm fine
This looks also partially related: https://github.com/cloudflare/workers-sdk/issues/7255
Good catch. I've already opened up a revert to get us back to the prior state (https://github.com/cloudflare/workerd/pull/3148).
We'll take another run at it working with remote DBs when we can.
GitHub
Build software better, together
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.