import suggestions not working as intended (vscode)

alaa · 2024-10-20T03:05:53.149Z

Hello, import suggestions (symbols not known to file) not working for me as intended on deno latest (vscode): When symbol not known:

A

alaaOP•10/20/24, 3:06 AM

when import statement written manually it works:

A

alaaOP•10/20/24, 3:07 AM

deno jsonc:

{
    "name": "test-lib",
    "version": "0.1.0",
    "tasks": {
        "install": "deno install --allow-scripts",
        "start": "deno run ./src/main.ts",
        "dev": "deno run --watch ./src/main.ts",
        "test": "deno test",
        "format": "deno run -A npm:@biomejs/biome format ./src",
        "lint": "biome lint --error-on-warnings ./src"
    },
    "imports": {
        "@biomejs/biome": "npm:@biomejs/biome@^1.9.4",
        "@std/assert": "jsr:@std/assert@1"
    },
    "nodeModulesDir": "auto",
    "publish": {
        "include": ["src", "LICENSE"],
        "exclude": ["src/tests"]
    },
    "exports": {
        ".": "./src/mod.ts"
    }
}

{
    "name": "test-lib",
    "version": "0.1.0",
    "tasks": {
        "install": "deno install --allow-scripts",
        "start": "deno run ./src/main.ts",
        "dev": "deno run --watch ./src/main.ts",
        "test": "deno test",
        "format": "deno run -A npm:@biomejs/biome format ./src",
        "lint": "biome lint --error-on-warnings ./src"
    },
    "imports": {
        "@biomejs/biome": "npm:@biomejs/biome@^1.9.4",
        "@std/assert": "jsr:@std/assert@1"
    },
    "nodeModulesDir": "auto",
    "publish": {
        "include": ["src", "LICENSE"],
        "exclude": ["src/tests"]
    },
    "exports": {
        ".": "./src/mod.ts"
    }
}

{
    "name": "test-lib",
    "version": "0.1.0",
    "tasks": {
        "install": "deno install --allow-scripts",
        "start": "deno run ./src/main.ts",
        "dev": "deno run --watch ./src/main.ts",
        "test": "deno test",
        "format": "deno run -A npm:@biomejs/biome format ./src",
        "lint": "biome lint --error-on-warnings ./src"
    },
    "imports": {
        "@biomejs/biome": "npm:@biomejs/biome@^1.9.4",
        "@std/assert": "jsr:@std/assert@1"
    },
    "nodeModulesDir": "auto",
    "publish": {
        "include": ["src", "LICENSE"],
        "exclude": ["src/tests"]
    },
    "exports": {
        ".": "./src/mod.ts"
    }
}

{
    "name": "test-lib",
    "version": "0.1.0",
    "tasks": {
        "install": "deno install --allow-scripts",
        "start": "deno run ./src/main.ts",
        "dev": "deno run --watch ./src/main.ts",
        "test": "deno test",
        "format": "deno run -A npm:@biomejs/biome format ./src",
        "lint": "biome lint --error-on-warnings ./src"
    },
    "imports": {
        "@biomejs/biome": "npm:@biomejs/biome@^1.9.4",
        "@std/assert": "jsr:@std/assert@1"
    },
    "nodeModulesDir": "auto",
    "publish": {
        "include": ["src", "LICENSE"],
        "exclude": ["src/tests"]
    },
    "exports": {
        ".": "./src/mod.ts"
    }
}

A

alaaOP•10/20/24, 3:09 AM

Problem only happens with remote libs (jsr/npm), no problem with local files (.ts)

A

alaaOP•10/20/24, 3:10 AM

versions latest on both deno and vscode extension

A

alaaOP•10/20/24, 11:06 PM

up

Á

Ánh Tạ•12/3/24, 3:36 AM

I encounter the same issue. Additionally, it is quite challenging to import a new declaration, such as a type or class, from a remote package.

P

PhinehasB•10/20/25, 8:30 PM

@alaa were you able to find a fix?

A

alaaOP•10/20/25, 10:06 PM

Yes, move to bun

M

Mr.Possumz•10/21/25, 6:24 PM

After adding a package, did you use deno install? As far as I've seen, Deno doesn't blanket download everything listed in the import map until you either tell it to via deno install or until you use it somewhere in the code.

If you manually update a file with the import line using the mapped alias then it should cache the dependency and start offering import suggestions as you would expect.

P

PhinehasB•10/22/25, 12:02 PM

Let me send a screenshot so you get what i mean.

Original message was deleted

P

PhinehasB•10/22/25, 12:03 PM

PPhinehasB Let me send a screenshot so you get what i mean.

P

PhinehasB•10/22/25, 12:04 PM

@Mr.Possumz this is what I meant

M

Mr.Possumz•10/22/25, 4:10 PM

yes because in the second screenshot you've downloaded the dependencies and installed them in your node modules project. If you run

deno install

deno install

deno install

deno install it will do the same thing

P

PhinehasB•10/22/25, 11:12 PM

YH

P

PhinehasB•10/22/25, 11:13 PM

These are two different projects. We have a call to look at it though

P

PhinehasB•10/22/25, 11:13 PM

I will be very happy @Mr.Possumz

S

Salty Kitsune•10/29/25, 2:06 AM

facing the same issue

SSalty Kitsune facing the same issue

P

PhinehasB•10/29/25, 11:17 AM

Seems its a general issue

S

Salty Kitsune•10/29/25, 3:09 PM

I noticed there is a related PR for the issue probably

https://github.com/denoland/deno/pull/28131

GitHub

fix(lsp): improve auto-imports to take into account only package ex...

TypeScript&#39;s auto-import implementation is implemented specifically for node_modules. Additionally, it seems to traverse through all the source files in a program then filter out any result...