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

hoary plover Sep 10, 2024, 8:39 PM

#

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

#

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

solar falcon Sep 11, 2024, 8:35 AM

#

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 @proud lynx

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.

proud lynx Sep 11, 2024, 9:32 PM

#

I can't reproduce it on latest canary - if you run with --unstable-kv it should all work correctly CC @hoary plover

solar falcon Sep 11, 2024, 10:55 PM

#

I'm seeing this issue on canary while using --unstable-kv in that PR I linked.

#

Let me raise an issue

hoary plover Sep 12, 2024, 4:09 PM

#

Let me try again

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