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"
  }
}

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

import handler from 'handler';

import handler from 'handler';

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

'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?

Deno Join

Chat about Deno, a modern runtime for JavaScript and TypeScript.

17KMembers

View on Discord

Using `Deno.FsFile.prototype.readable` with `Response`I was trying to stream a file into a response with the snippet: ```ts const file = await Deno.open(p react-helmet-async missing HelmetProvider exportI'm on the canary version testing out jsxImportSourceTypes and ran into an issue when switching to u