Root path suport

[allangomes]

.
├── package.json
├── Lib
│   ├── Components
│   └── ...
├── App
│   ├── Customer
│   └── ...

utils

import { List }  from 'Components'

app

import { Customer }  from '~/Customer'

Workspace Settings

{
    "npmintelisense.paths": [
             "./node_modules", 
             "./Lib", 
             { "prefix": "~/",  "path":"./App" }
    ]
}

where . is path of Package.json

[vasa-chi]

Given facebook/create-react-app#1065 this feature would be indeed awesome.

[mkg0]

i think specific path options are welcome but vscode uses jsconfig.json file for resolving modules like this:

// jsconfig.json
{
    "compilerOptions": {
        "target": "ES6",
        "module": "commonjs",
        "allowSyntheticDefaultImports": true,
        "baseUrl": "./",
        "paths": {
          "~/*": "App/*",
          "*": [
              "Lib/*",
          ]
        }
    }
}

microsoft/vscode#14907 (comment)

it is better supporting default resolver. herewith we can peek or goto directly modules by clicking.

( also jsconfig.json schema: https://github.com/SchemaStore/schemastore/blob/master/src/schemas/json/jsconfig.json )

[alvelig]

I would suggest that import '/components' referred to import '{rootPath}/src/components' by default.

For now ejected and use .babelrc:

{
  "plugins": [
    ["babel-root-slash-import", {
      "rootPathSuffix": "src"
    }]
  ]
}

This is fully compatible with Intellij Idea and as far as I can see does not interfere with other ways of defining absolute or relative paths.

[Ronsku]

I would also like to have intellisense for typescript custom paths that are generated in the tsconfig.json like this:

{
  "compileOnSave": false,
  "compilerOptions": {
    "paths": {
      "@app/*": ["./app/*"],
      "@src/*": ["./*"]
    },
  ...

Usage for example:
import { RootReducer } from '@app/app.reducers'; // This provides currently no path intellisense