VS Community and TS: auto-import adds '.js' extension to the module name, while auto completion not

[AbuDawood]

visual studio 2019 community,
for the autocomplete during import the suggested modules are as expected (module name without extension), However, when typing ex. a class name and want to auto-import the incloser module it gets added with .js extension !! what's wrong

• screenshot for autocomplete the import syntax
  

• screenshot for auto import suggestions
  

[DanielRosenwasser]

So some context: for path completions, we currently we find the first existing import that's relative, and then figure out if it uses an extension. If so, we provide paths with .js files: #20624

However, there was talk of following up and making extensions for import paths configurable: #19019 (comment)

[AbuDawood]

Thank you @DanielRosenwasser for your reply.
The issue is that I am working on a project that uses Webpack i.e. supports the import of modules with extensionless syntax.
According to the mentioned situation, the provided option is not helpful.

[daramasala]

So some context: for path completions, we currently we find the first existing import that's relative, and then figure out if it uses an extension. If so, we provide paths with .js files: #20624

However, there was talk of following up and making extensions for import paths configurable: #19019 (comment)

Mine is a typescript project. None of my imports use '.js' (they are all without any extension) yet new auto imports are created with '.js'.
I have another project with exactly the same tsconfig.json file and there, imports are created without an extension.
I would be happy for some guidance on which files/configurations would help troubleshoot the issue (as I said, I don't think it's the tsconfig file since the same file in a different project yields extensionless imports).

[andrewbranch]

Lots of things around this have changed since this issue was opened. Certain compiler options indicate that extensions are required by the module system where the code is intended to run. Beyond that, there are editor preferences, and when not set and the compiler options allow multiple options, an attempt to match the style of the existing file is made. Given how many features have been added (and bugs fixed), I’m going to close this. Feel free to open a new one with complete repro steps if you’re still experiencing buggy or confusing behavior.