[no-useless-undefined] incorrect fix for ts `Promise.resolve(undefined)`

Repository metrics

Stars

5,022 stars (5,022 stars)

PR merge metrics

Avg merge 1d 16h (Avg merge 1d 16h)399 merged PRs in 30d (399 merged PRs in 30d)

Description

Promise.resolve(undefined) // Promise<undefined>

Promise.resolve() // Promise<void>

Contributor guide

Research direction

Investigate the `no useless undefined` rule in `rules/no useless undefined.js`. The rule currently removes `undefined` arguments from function calls, but for `Promise.resolve(undefined)`, removing `undefined` changes the return type from `Promise<undefined>` to `Promise<void>`. The rule should be updated to preserve `undefined` when it affects the type semantics, possibly by checking if the function's signature expects `undefined` or if the context involves `Promise`. Review the rule's logic for removing `undefined` and add an exception for `Promise.resolve` and similar cases where `undefined` is significant.

Tech stack

javascript

Domain

developer experiencetooling

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

ESLint plugin basicsJavaScript Promise types

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60