microsoft / microsoft/TypeScript
Go to Definition for Non JS/TS File Imports
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
From https://github.com/Microsoft/vscode/issues/24276
Issue
Users of tools such as webpack often load non js/ts assets, such as css or images, using require or import:
require('./main.css');
import './image.png'
...
Operations such as go to definition currently do not work on these paths
Proposal
go to definition on these resource paths should try to open the corresponding resource in the editor.
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 by tracing the go-to-definition handling for require and import paths, using the CSS and image examples in the issue as the initial cases. Determine where non-JavaScript/TypeScript resources are rejected or left unresolved, then verify that selecting such a path opens the corresponding resource in the editor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100