TS-Check: cannot find module

[NileDaley]

TypeScript Version: 3.1.3

Code

//@ts-check
const { axios } = require('axios')

Expected behavior:
Axios will be required from './node_modules/axios/index'

Actual behavior:
Error shown is cannot find module 'axios' despite axios being installed. Note that this problem is not axios specific, it occurs with any module. However, if I use the following syntax then it is required correctly.

//@ts-check
const { axios } = require('./node_modules/axios/index')

Screenshots:

The error:

No error when using path:

TypeScript debug error:

The stack trace looks like #27867.
However, I can't reproduce the crash, even on 3.1.3. I'm testing with a project that consists of just a file a.js containing:

// @ts-check
const { axios } = require('axios')

Your project may be different because of other files you have, particularly a tsconfig.json or jsconfig.json.
I also don't see the error message you're seeing. I see a different error:

[ts] Type 'typeof import("/home/andy/sample/js/node_modules/axios/index")' has no property 'axios' and no string index signature. [2459]

This is with axios 0.18.0 installed.

[NileDaley]

Here's the contents of my jsconfig.json file in the project root

{
    "compilerOptions": {
        "target": "ES6",
        "lib": ["es5", "es6", "es7"]
    }
}

However, having tested again with the jsconfig.json file deleted, it still produces the same error. Although, in some projects on my system the module will be required fine. I should also note - just in case it makes any difference - that this bug is occuring within vscode 1.28.2

[NileDaley]

@Andy-MS So i've been testing, and I've found something else which is strange

The project is laid out like this:

project
    subprojectA
        folderA
            index.js 
            node_modules
        folderB
        ....
    subprojectB
    ....
    jsconfig.json

If i have the project folder open in vscode and open subprojectA/folderA/index.js, then the error will be thrown. However, if I open the folderA directly in vscode, then the module will be required correctly.

Could the issue be related to the fact that there are so many subProject folders whose child folders also contain node_modules?

[NileDaley]

@Andy-MS Any update on this issue?