microsoft / microsoft/TypeScript
auto import always uses relative (to the current file) module paths in presense of baseUri
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
back in a day it used to be different
- at first it was always an absolute path (that is without "./" or "../" in it) relative to the
baseUri - then starting at some point it began to always show a popup with 2 options: absolute or relavive
- now (since like a week ago or so) it just always uses a relative path with "./" and "../" to the current file no matter what, without asking, which is very frustrating and annoying
how can i get the auto import to use absolute paths like it was back in the day?
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
No file, test, or entry point is named. Start by reproducing auto-import generation in a TypeScript project that uses baseUri, then trace the language-service behavior for relative versus absolute module specifiers. Done means the intended import style is restored or an explicit configuration path is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100