JSR package "@oak/oak@^17.1.6" is not installed or doesn't exist.deno(not-installed-jsr)

[MyBjMy]

Description

There seems to be an inconsistency between VS Code Deno extension diagnostics and the deno lint / CLI behavior.

When using the Deno VS Code extension, I get the following error:

JSR package "@oak/oak@^17.1.6" is not installed or doesn't exist. deno(not-installed-jsr)

However, when I run deno lint or execute the project using the Deno CLI, everything works fine — the package is correctly resolved, and no such error appears.

Expected Behavior

VS Code’s Deno language server should correctly recognize and resolve JSR packages (like @oak/oak@^17.1.6), matching the behavior of deno lint and the Deno CLI.

Actual Behavior

The VS Code extension reports a false positive diagnostic (deno(not-installed-jsr)), even though the package exists and works correctly when running or linting the code with Deno CLI.

Environment

Deno version: deno --version

VS Code version: (e.g. 1.95.0)

Deno extension version: (e.g. 3.39.0)

OS: (e.g. macOS 14.5 / Windows 11 / Ubuntu 24.04)

Additional Context

The issue might be related to the language server’s package resolution for JSR imports, especially when using version ranges like ^17.1.6.

Would you like me to make it a bit shorter or more formal (for example, if you plan to post it on the denoland/vscode_deno
repo)?