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:devGitHub
GitHub - zemili-group/moonrepoV3: Deno monorepo on deno deploy all ...
Deno monorepo on deno deploy all things zemil-group - zemili-group/moonrepoV3
4 Replies
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 @bartlomiejuGitHub
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.
I can't reproduce it on latest canary - if you run with
--unstable-kv it should all work correctly CC @Sean KnowlesI'm seeing this issue on canary while using
--unstable-kv in that PR I linked.
Let me raise an issueLet me try again
Pretty sure this is now sorted, the fix above worked