microsoft/TypeScript

Intellisense for TS/JS package.json imports and exports

Closed this issue · 3 comments

valler commented

One should be able to follow the urls/paths/specifiers in a package.json imports or exports field, etc. Basically one should expect the same DX for these as for TS/JS module imports.

Example:

{
  "imports": {
    "#foo": "@six-seven/cmd-click-me-bro",
    "#bar": "./i-want-to-be-resolved/index.ts"
  },
  "exports": {
    "./baz": "./give-me-intellisense.ts"
  }
}

There's not really a great place for this, architecturally:

  • node is the real arbiter of truth here, but doesn't have an LSP at all
  • TypeScript is the next-best provider, but isn't operating in package.json contexts
  • JSON Schema is providing LSP here, but can't do dynamic file-based stuff

Barring a lot more feedback, this is basically out of scope for everyone. Hopefully no one has an export map complicated enough to warrant this 😬

valler commented

It's not really about complexity; more about the convenience of links, so you wouldn't need to switch to the explorer.

This issue has been marked as "Out of Scope" and has seen no recent activity. It has been automatically closed for house-keeping purposes.