Auto-import suggests deep nested paths over the top-level exports.

[just-boris]

• VSCode Version:1.51.1
• OS Version: MacOS 10.15.7

Steps to Reproduce:

Given the following project structure

// node_modules/my-lib/internal/component.d.ts
export class Component {}

// node_modules/my-lib/index.js
export { Component } from './internal/component';

When I am trying to use "Component" class, the editor automatically suggests the import from 'my-lib/internal/component' path.

This may lead to issues, where users inadvertently use private paths, which were not intended by package authors.

P.S. I found a relevant issue #35395, however that was about maintaining some sort of "exclude list" manually, whereas this report is about the editor automatically preferring top-level paths over the internal folders out of the box.

Does this issue occur when all extensions are disabled?: No suggestions at all when extensions are disabled.

[andrewbranch]

@just-boris can you provide an example repo that demonstrates this problem? Reason I ask is that I’ve seen this functionality work correctly for a long time, so it must be something specific to your packages/settings/??? that's causing the issue.

[just-boris]

Hello!

Seems like it was the issue on my side, I confused default and named exports.

When I fixed this, the editor gives no suggestions, however it starts suggesting the same import if one was already used in the project.

I think, this works as expected and I will close the issue.