Deno•2y ago

Deno LSP Issue with import maps?

I've been using an import map throughout my project like this:
deno.json file at the projects' root that has a map like this:

{
  "imports": {
    "atlas": "https://deno.land/x/atlas_sdk@v1.1.1/mod.ts",
    "handler": "./source/server/handler.js"
  }
}

{
  "imports": {
    "atlas": "https://deno.land/x/atlas_sdk@v1.1.1/mod.ts",
    "handler": "./source/server/handler.js"
  }
}

{
  "imports": {
    "atlas": "https://deno.land/x/atlas_sdk@v1.1.1/mod.ts",
    "handler": "./source/server/handler.js"
  }
}

{
  "imports": {
    "atlas": "https://deno.land/x/atlas_sdk@v1.1.1/mod.ts",
    "handler": "./source/server/handler.js"
  }
}

and then for example, import the handler.js file like this:

import handler from 'handler';

import handler from 'handler';

import handler from 'handler';

import handler from 'handler';

Although its still working just fine. I now see a red curly underline under

'handler'

'handler'

'handler'

'handler'

or any other file that's being used in the same way. And when I hover over it, it says "Relative import path "handler" not prefixed with / or ./ or ../ deno(import-prefix-missing)".
Am I doing something wrong or is it just an LSP bug?

No replies yetBe the first to reply to this messageJoin

Deno LSP Issue with import maps?

Similar Threads

Similar Threads

Similar Threads