microsoft / microsoft/TypeScript
Organize Imports should group package.json `imports` with local path ones
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 117
Description
I would like the Organize Imports action to group Node.js' package.json imports, which are prefixed with #, after regular node_modules packages
Current Behaviour
import { } from "package";
import { } from "#file2.js";
import { } from "./file.js";
Organizes to:
import { } from "#file2.js";
import { } from "package";
import { } from "./file.js";
Requested Behaviour
I think it would make more sense if the local imports were grouped after the package import (I don't have any preference over the order of ./file.js and #file2.js themselves), e.g.:
import { } from "package";
import { } from "#file2.js";
import { } from "./file.js";
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 at the Organize Imports implementation and its existing tests; the issue does not name specific files or test cases. Reproduce the shown ordering, then verify that package imports precede # imports and local path imports according to the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100