daidodo/format-imports

Improve importType support (`import type` vs`import { type }`)

Open

#78 opened on Oct 29, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (4 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (51 stars)
PR merge metrics
 (PR metrics pending)

Description

VSCode auto-import does not reliably put import types in a separate import tag, ie. depending on what's pre-existing, it may do different style :

import type { A } from '.foo1'
import { type B } from '.foo2'
import { type C, bar } from '.foo3'
import { type D, type E, baz, qux } from '.foo4'

It would be great if format-imports could fix it by formatting them like this:

import type { A } from '.foo1'
import type { B } from '.foo2'
import type { C } from '.foo3'
import { bar } from '.foo3'
import type { D, E } from '.foo4'
import { baz, qux } from '.foo4'

For now, we have importType that will properly groups import type, but won't do anything when type is inside the bracket.

Thanks!

Contributor guide

Research direction
Examine how `importType` currently groups imports and extend it to handle `import { type }` syntax by splitting type only imports into separate `import type` statements.
Tech stack
typescript
Domain
developer experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65