Preference for including file extension on auto imports

[mjbvz]

Search Terms

• Auto imports
• Preferences
• File extensions

Suggestion

From microsoft/vscode#51259

Add a preference to include file extensions on auto import paths.

Use Cases

File extensions are required when working with browsers.

Examples

a.js:

export const abc = 123;

b.js

abc|

Trigger auto import on abc in b.js to get:

import { abc } from './a.js'

abc

[mhegazy]

PRs welcomed for adding support of file extension preference

[andrewbranch]

This has actually existed in TS since #26177, but was never added to typescript-language-features. I just tried it and confirmed it works. From conversation in #28288, though, it sounds like we should maybe consider setting .js endings as the default for JS projects? @mjbvz @DanielRosenwasser thoughts? (Edit: Actually, I think this would still be a surprising default for most JS users—I don’t think it’s common in Node, and most frontend users still use a bundler.)

[wsmd]

Question related to microsoft/vscode#90405 - Is there an existing configuration that can achieve the same behavior for autosuggest when typing the import statement manually?

For example:

{
  "javascript.preferences.importModuleSpecifierEnding": "js",
}

import { someFunction } from './|';
                                ^ when picking a file from suggestions here,
                                  the file extension seems to always be omitted

[andrewbranch]

I can’t immediately think of a reason why we shouldn’t respect that same setting for module specifier completions. @wsmd would you mind opening a new bug for this?

[wsmd]

Thanks @andrewbranch! Will do! I think it would be nice to have importModuleSpecifierEnding applies for both auto-imports and manual import suggestions 👍

Reported here https://github.com/microsoft/vscode/issues/97106