Path based Code navigation to /index.js seems broken

• VSCode Version: 1.42.1
• OS Version: Mac OS

Steps to Reproduce: Code navigation seems broken when you import by path and the file is actually in an index.js file. There are a couple of scenarios relevant to developing in react-native

1. import from another package in a monorepo import SomeComponent from 'common-lib/Router, when the file is packages/common-lib/src/Router/index.js
2. import in the same package import SomeComponent from 'modules/Router, when the file is src/modules/Router/index.js
3. import SomeComponent from 'modules/Router, when the file is not actually index.js src/modules/Router/index.ios.js and src/modules/Router/index.android.js

In general, what works is loading a file name by name (not an index.js file) What doesn’t work is loading a file by path that is actually an index.js, index.native.js, index.ios.js, index.android.js etc file

My code structure is

root
    packages
           mobile
           server
                src
                       server
                       shared
           common-lib

There is some history here that is not ideal. But ok.

packages/server jsconfig.json

{
	"compilerOptions": {
		"target": "es2017",
		"allowSyntheticDefaultImports": false,
		"baseUrl": ".",
		"paths": {
			"common-lib/*": ["../common-lib/*"],
			"mobile/*": ["../mobile/*"],
			"modules/*": ["./src/shared/modules/*"],
			"components/*": ["./src/shared/components/*"],
			"router/*": ["./src/shared/router/*"],
			"server/*": ["./src/server*"],
			"App": ["./src/App"]
		}
	},
	"exclude": ["node_modules", "../../node_modules", "build"]
}

Does this issue occur when all extensions are disabled?: Yes

[IllusionMH]

That’s Node.js “feature” to check folder/index.js if folder referenced, using "moduleResolution": "node" should enable this behavior in TS.

However this won’t help with e.g. index.android.js but I doubt that since this should be handled by tooling, maybe vscode-react-native might handle these specific cases.

[orta]

I think so yeah, it could recommend making a jsconfig with target: node?

Perhaps something like?

import SomeComponent from ...'common-lib/Router'

/// TS:XYZ - Could not find a file at 'common-lib/Router', but  `common-lib/Router/index.js` was found - do you want to set `moduleResolution: node`?