VSCode auto-import ignores typescript.preferences.importModuleSpecifierEnding when using a path from the package.json imports

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

• VS Code Version: 1.95.1
• OS Version: MacOS 14.7

I have these settings in VSCode:

{
   "javascript.preferences.importModuleSpecifierEnding": "minimal",
   "typescript.preferences.importModuleSpecifierEnding": "minimal"
}

I have these setting in my package.json:

"imports": {
    "#src": ["./src/index.ts", "./src/index/tsx"],
    "#src/*": [
      "./src/*",
      "./src/*.ts",
      "./src/*.tsx",
      "./src/*/index.ts",
      "./src/*/index.tsx"
    ]
  },

I have these settings in my tsconfig.json

"target": "esnext",
"module": "esnext",
"moduleResolution": "bundler",

However, when I auto-import something that starts with #src/, it automatically appends a .js to the import (or a .ts if I have allowImportingTsExtensions on. This is ignoring my settings to use the minimum module specifier ending I set in VSCode.

It looks like the addition of the .ts functionality was added in this bugfix: https://github.com/microsoft/TypeScript/issues/52167. I'm not sure why it wasn't set to respect the vscode settings.

Reproduce the auto-import behavior using the reported package.json imports, tsconfig.json settings, and VS Code preferences. Start by tracing TypeScript's auto-import module-specifier handling, then verify that imports using paths such as #src/ respect the configured minimal ending without regressing the existing .js or .ts behavior.