Sean Knowles
Sean Knowles5w ago

Deno.Kv() not connecting latest Canary, if I downgrade to RC1 then it works, but then FE don't work.

Steps to reproduce: Small issue, currently blocked as the latest Canary release my backends won't connect to KV locally. If I downgrade to RC1 my frontends won't run. So I am stuck with either of my backends or frontends working depending on the version I am running. - export deno KV export DENO_KV_ACCESS_TOKEN =abc123 - Clone: https://github.com/zemili-group/moonrepoV3 - in root run: deno run opsap-backend:dev
GitHub
GitHub - zemili-group/moonrepoV3: Deno monorepo on deno deploy all ...
Deno monorepo on deno deploy all things zemil-group - zemili-group/moonrepoV3
No description
4 Replies
iuioiua
iuioiua4w ago
Can you please open an issue? I think I'm running into the same issue in https://github.com/denoland/saaskit/pull/685. I'm seeing Deno.openKv() as being undefined even when using --unstable-kv. CC @bartlomieju
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.
From An unknown user
From An unknown user
From An unknown user
bartlomieju
bartlomieju4w ago
I can't reproduce it on latest canary - if you run with --unstable-kv it should all work correctly CC @Sean Knowles
iuioiua
iuioiua4w ago
I'm seeing this issue on canary while using --unstable-kv in that PR I linked. Let me raise an issue
Sean Knowles
Sean Knowles4w ago
Let me try again Pretty sure this is now sorted, the fix above worked