Property 'openKv' does not exist on type 'typeof Deno'. VSCode

[sweet sable]

Such as the title say, I cant get the LSP to recognize openKv in the Deno namespace...

deno 1.32.5+78b630d (canary, x86_64-apple-darwin)
v8 11.2.214.15
typescript 5.0.3

Any idea ?

[grizzled karma]

do you have unstable enabled?

[worthy finch]

Same here

{
  "deno.enable": true,
  "deno.unstable": true
}

[oak patio]

I've notice that that is not enough. I have use the --unstable flag in the deno run cli command.

[acoustic pasture]

I can't access any unstable APIs in VSCode either. Even with the suggested .vscode/settings.json settings.

# deno --version
deno 1.33.1 (release, x86_64-pc-windows-msvc)
v8 11.4.183.1
typescript 5.0.3

[acoustic pasture]

Are there any other places to enable unstable?

[acoustic pasture]

I have unstable enabled in VSCode, but the same error is still there. @grizzled karma is it possible this is a Windows problem?

[worthy notch]

I'm experiencing the same thing but on mac os

[oak patio]

No issue here on Windows. try refreshing deno lsp by ctrl+shift+p then Deno: Initialize Workspace

I've used that in past to clear such issues.

[worthy finch]

still same issue on macos. tried:

• reinstalling the extension
• building and running the extension from source
• hardcoding unstable in the extension source code
• upgrading the deno executable

[oak patio]

What version of Deno are you running?

deno -V

How were you able to modify the extension? Not a good idea IMHO

[worthy finch]

deno --version
deno 1.33.1 (release, aarch64-apple-darwin)
v8 11.4.183.1
typescript 5.0.3

[worthy finch]

I just modified the source code while running the extension from source. I don't run it from source anymore

[oak patio]

Are you sure deno is enabled in the project, It is not enough to just have the /.vscode/settings.json ,
you must open the Command Pallet (Ctrl+Shift+P),
and run the Deno: Initialize Workspace Configuration

If it is initialized, you should see Deno 1.33.1 at the far right bottom status-bar in VSCode.

[oak patio]

Can you run the code with deno run -A --unstable yourmodname.ts. ?

Sometimes a successful run will refresh the cache.

What is missing is lib.deno.unstable.d.ts

[acoustic pasture]

Relevant issue: https://github.com/denoland/deno/issues/18907

[worthy finch]

^ Tried the versions he mention. No difference. Tried a few more versions. Also tried uninstalling deno completely, verified VSCode could not find the binary. Then reinstalled but through homebrew this time. Issue persists 🤷‍♂️

[worthy finch]

Runs fine with the flag, but the issue persists in the editor

[worthy finch]

Where can I find this file and what populates it?

[oak patio]

It should have populated automatically with the deno: unstable = true setting.

[worthy finch]

Populate where?

[oak patio]

In the cache. I think this is related
https://github.com/denoland/deno/issues/18907

[worthy finch]

Where is the cache?

[acoustic pasture]

Should we wait to roll forward?

[worthy finch]

Does rolling back solve the issue for you?

I have the issue in every version of Deno I try. Just tried 1.21.0 even

Going to try different versions of the extension as well

[worthy finch]

Nothing so far. Going to run deno from source and check the logs to see when/if the unstable flag gets lost

[worthy notch]

It's quite strange, in one project I don't get this error and in another I do.

[worthy finch]

🤦‍♂️

[worthy finch]

created a new directory with only an index.ts, did the init workspace config

now it works

[worthy notch]

weird, I’ll try that

[worthy finch]

Found the culprit

import { json, serve } from "https://deno.land/x/[email protected]/mod.ts";

Commenting out this import solves the issue

I suppose it overrides the .d.ts

switched to import { serve } from "https://deno.land/[email protected]/http/server.ts"; instead.

[acoustic pasture]

I cannot believe that simply removing the dependency I had on Sift actually fixed the problem! Thank you for looking into this for us!!

I used code from the old Deno Deploy Discord Application Command tutorial which had Sift.

[worthy finch]

same lol

[acoustic pasture]

Deno.Kv + Discord Application Commands = ❤️

[sweet sable]

This is still not fixed on latest Canary version, the LSP randomly doesnt recognize OpenKV...

i was working with it without any problem all morning but now its gone

Openned this issue for tracking https://github.com/denoland/deno/issues/19035

[worthy notch]

yeah not really sure what’s going on here