Unstable comment in import
Open
Nobody has claimed this yet.
area:comments
area:idempotency
lang:javascript
- Dominant language
- JavaScript
- Stars
- 52.3k
- Forks
- 5k
- Avg merge
- 19h 2m
- Merged PRs (30d)
- 117
Description
Prettier 1.10.2
Playground link
Input:
import {a,
b
/*one*/ as
//two
B } from ""
Output:
import {
a,
/*one*/ //two
b as B
} from "";
Second Output:
import {
a, //two
/*one*/ b as B
} from "";
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
Reproduce the case from the linked Playground using the shown JSX import and compare both reported outputs. Start by tracing the formatter's import-comment handling from this minimal example. Done means the comment placement is deterministic and the regression is covered by the project's existing formatter tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100