microsoft / microsoft/TypeScript
Hovering on imported module shows path from TypeScript folder.
Open
Nobody has claimed this yet.
Awaiting More Feedback
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
TS Template added by @mjbvz
TypeScript Version: 3.9.6
Search Terms
- quickinfo
- types
- javascript
- VSCode Version: 1.46.1
- OS Version: Windows 10
Steps to Reproduce:
- Require modules like yargs, validate in a nodejs project. (Installed in project folder)
- On hover, TypeScripts node_modules path is shown instead of project's node_modules folder.
- Packages not in TypeScript's node_modules folder has no such issue.
Hovering on yargs:
Hovering on chalk:
Does this issue occur when all extensions are disabled?: Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported reproduction in a Node.js project using yargs or chalk and inspect the hover/Quick Info behavior for imported modules. No source file or test is named in the issue; done means the hover resolves packages from the project's node_modules folder rather than TypeScript's node_modules folder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100