Intellisense fails to detect package.json import paths

[anthonyma94]

🔎 Search Terms

• path completion
• node.js import path intellisense

🕗 Version & Regression Information

• Tested on TS 5.7.3 with VSC 1.98.0 and 5.8.2 with VSC 1.98.2

⏯ Playground Link

https://github.com/anthonyma94/path-completion-repro

💻 Code

package.json

  "imports": {
    "#foo/*": {
      "types": [
        "./src/foo/*.ts",
        "./src/foo/*"
      ],
      "default": [
        "./src/foo/*"
      ]
    }
  },

src/foo/test.ts

export const testFunc = () => {}

src/index.ts

import { testFunc } from "#foo/test";

testFunc();

🙁 Actual behavior

Repro for #52460.

Path completion intellisense kicks in for symbol resolution:

But not path resolution:

🙂 Expected behavior

I expect Intellisense to work for both scenarios.

Additional information about the issue

No response

[mkvlrn]

I've reached a scenario that is working for me but I really don't think it is supposed to be done this way, because I ended up not needing file extensions for imported modules while not in bundler moduleResolution:

/** package.json */

{
// ...
  "type": "module",
  "imports": {
    "#*": {
      // just worked like this, didn't need a "proper" recursive glob like "./src/**/*.ts"
      "dev": "./src/*.ts",
      // same here
      "default": "./build/*.js"
    }
  },
// ...
}

/** tsconfig.json */

{
// ...
  "customConditions": ["dev"], // this was key
  "esModuleInterop": true,
  "isolatedModules": true,
  "lib": ["ESNext"],
  "module": "NodeNext",
  "moduleResolution": "nodenext",
  "target": "esnext",
// ...
}

/** src/lib/basic-math.ts */

export function add(a: number, b: number): number {
  return a + b;
}

/** src/main.ts */

import { add } from "#lib/basic-math";

console.log(`2 + 2 = ${add(2, 2)}`);

In main.ts I get intellisense if I manually add the "base" #lib/, but it does not suggest adding the base path itself.

Running code works fine:

• without the build step, using dev conditions to import the ts files, using node to strip types (node -C dev src/main.ts)
• after the build step, without changing import conditions (node build/main.js)

My environment:

• node 23.11
• typescript 5.8.2
• vscode 1.98.2

[RyanCavanaugh]

Closing language service bugs related to the 6.0 implementation. For more information, see #62827