Inconsistent JavaScript Intellisense / not working

[mudrz]

• VSCode Version: Version 1.13.1
• OS Version: macOS Sierra 10.12.5 (same on Win10)

Steps to Reproduce:

What I am trying to do:
I am using webpack aliases and want to utilize VS Code Intellisense for them
webpack.config.js

...
alias: {
...
App: path.resolve(__dirname, 'ClientApp'),
...
}
...

ClientApp Folder structure

jsconfig.json

{
  "compilerOptions": {
    "target": "es6",
    "baseUrl": ".",
    "paths": {
      "App": ["./"]
    }
  },
  "exclude": ["dist"]
}

Some functions like deleteProperty are not recognized if using alias App

but are recognized if using relative paths

other functions are recognized (in same folder, completely same format used)

additionally using index.js with re-exports

does not work even with relative paths (IOptions.js has a default export object, recognized only in the last format)

import { IOptions } from 'App/models';

import { IOptions as IOptions2 } from './models';

import IOptions3 from 'App/models/IOptions';

import IOptions4 from './models/IOptions';

Are these configuration issues or?

[zanza00]

I had a similar problem #30122

my solution is the following jsconfig.json

{
  "compilerOptions": {
    "target": "ES6",
    "allowSyntheticDefaultImports": true,
    "jsx": "react",
    "module": "commonjs",
    "baseUrl": ".",
    "paths": {
      "*": [
        "*",
        "app/*"
      ]
    }
  },
  "include": [
    "app/**/*.js"
  ]
}

the important bits are module, baseurl and path

Hope this helps 😄

[mudrz]

@zanza00 , thanks zanza, unfortunately the result was the same (I tested quite a few jsconfig.json configurations)

I created a repo with test files to illustrate the issue (with 2 folders with different jsconfig.json files)
https://github.com/mudrz/js-intellisense-tests.git

There was no difference (this time I tested it on Windows 10)

[mjbvz]

@mudrz We don't fully support the proposed export from syntax yet. This is being tracked upstream by microsoft/TypeScript#4813

I believe you also have to use globs in the paths. Try something like this:

{
  "compilerOptions": {
    "target": "ES6",
    "allowSyntheticDefaultImports": true,
    "jsx": "react",
    "module": "commonjs",
    "baseUrl": ".",
    "paths": {
      "App/*": [
        "./*"
      ]
    }
  },
  "include": ["**/*.js"]
}

[mudrz]

@mjbvz , nice, thanks, I wasted so much time on this trying different jsconfig combinations, didn't know that the key also needs to use globs

I tested both configurations and can confirm that Intellisense works in this case (-the export from syntax)

{
  "compilerOptions": {
    "target": "es6",
    "baseUrl": ".",
    "paths": {
      "App/*": ["./*"]
    }
  },
  "exclude": ["dist"]
}