`deno lsp` does not understand bare imports without prefix

Even in minimal project, freshly created from a template, Deno marks imports as errors and doesn't understand them.

E.g.

deno run --allow-read --allow-write --allow-env npm:create-vite-extra@latest

deno run --allow-read --allow-write --allow-env npm:create-vite-extra@latest

"
Open

src/main.ts

src/main.ts

in the editor which uses

deno lsp

deno lsp

, and an error pops up:

import { createApp } from 'vue'

import { createApp } from 'vue'

Relative import path "vue" not prefixed with / or ./ or ../
(import-prefix-missing)

Relative import path "vue" not prefixed with / or ./ or ../
(import-prefix-missing)

Adding a source map doesn't make a difference.
Any ideas?

Deno•3y ago•

2 replies

Even in minimal project, freshly created from a template, Deno marks imports as errors and doesn't understand them.

E.g.

deno run --allow-read --allow-write --allow-env npm:create-vite-extra@latest

deno run --allow-read --allow-write --allow-env npm:create-vite-extra@latest

"
Open

src/main.ts

src/main.ts

in the editor which uses

deno lsp

deno lsp

, and an error pops up:

import { createApp } from 'vue'

import { createApp } from 'vue'

Relative import path "vue" not prefixed with / or ./ or ../
(import-prefix-missing)

Relative import path "vue" not prefixed with / or ./ or ../
(import-prefix-missing)

Adding a source map doesn't make a difference.
Any ideas?