sindresorhus/eslint-plugin-unicorn

Rule proposal: `no-non-exists-builtin-properties`

Closed

#2,225 opened on Dec 1, 2023

View on GitHubContributor guide
 (2 comments) (1 reaction) (0 assignees)JavaScript (468 forks)user submission
help wantednew rule

Repository metrics

Stars
 (5,022 stars)
PR merge metrics
 (Avg merge 1d 16h) (399 merged PRs in 30d)

Description

Description

I've made two mistakes recently when using Object.entries(), they are just typos, but spell check didn't pick them since they are words.

I used Object.entires() in one place, and Object.entire() in another place :smile: .

Fail

Math.NON_EXISTS_PROPERTY

Promise.nonExistsMethod()

Function.once()

Pass

Math.PI

Promise.race()

Additional Info

No response

Contributor guide

Research direction
Review existing rules in eslint plugin unicorn to understand the structure. Create a new rule file that checks for non existent properties on built in objects like Math, Promise, etc. Use AST node types like MemberExpression. Write tests for passing and failing cases. Refer to the ESLint custom rules documentation and the plugin's rule testing utility.
Tech stack
javascriptnodejs
Domain
developer experience
Issue type
Feature
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.
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
JavaScriptESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70