microsoft / microsoft/TypeScript

Organize Imports should group package.json `imports` with local path ones

Open
#52,515 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Awaiting More Feedback Suggestion
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.