PathIntellisense: path-intellisense.mappings doesn't work / not used correctly

@ChristianKohler i figured out that you can reproduce this issue by installing both path-intellisense and npm-intellisense.

I think the problem comes from npm-IntelliSense

It seems that vscode’s import path quick suggestions break mappings After I added

"typescript.quickSuggestionsForPaths": false,

and with

"path-intellisense.mappings": {
     "@": "${workspaceRoot}/app"
 }

it started to provide correct suggestions for import from '@/'

having this issue without npm-intellisense installed

absolute mapping is not working either for me. Don’t have npm intellisense extension…

Disable npm intellisense extension and add

"typescript.quickSuggestionsForPaths": false,

it works for me now

Got the same issue.

Here is my config:

"path-intellisense.mappings": {
    "/": "${workspaceRoot}/main/src",
    "controllers": "${workspaceRoot}/main/src/controllers",
    "components": "${workspaceRoot}/main/src/components"
}

When I use it with elements’ attrs it works

It also works with exports

But the only thing I need to be work – doesn’t work 😃

same here: trying to map my app/ directory to be used without prefix in my code:

{
    "path-intellisense.mappings": {
         "/": "${workspaceRoot}/app"
     }
}

both import '/' and import '' don’t provide suggestions

mappings not work if npm-intellisense installed

@lucasbento I am sorry. I don’t mean to order anyone to do anything. My words are inappropriate.

@ChristianKohler as you said. It is work. But is not similar behaviour as how alias in webpack work. for example.

I expect "*": "${workspaceRoot}/main/src" instead of "components": "${workspaceRoot}/main/src/components"

Then I can type whatever import x from components or import y from containers. In your case. Should I need to keep maintain project structure?

same issue and npm-intellisense isn’t installed and there is no such thing as typescript.quickSuggestionsForPaths.

have anyone got any success on this ?

I got mine to work by disabling a few default path suggestions

    "typescript.suggest.paths": false,
    "javascript.suggest.paths": false,
    "path-intellisense.mappings": {
       "/": "${workspaceFolder}",
      "components" :  "${workspaceFolder}/client/src/components"
    },

Depending on which language you are working in you may have to disable the default setting {language}.suggest.paths You can make the settings specific only to a workspace which makes it more convenient.

I didn’t need to disable any other extension.

I’ve uninstalled npm-intellisense and getting same error