rahuldkjain/github-profile-readme-generator

fix ESLintError warnings in local dev environment

Open

#279 opened on Oct 18, 2020

View on GitHub
 (4 comments) (0 reactions) (1 assignee)JavaScript (19,657 stars) (5,899 forks)batch import
enhancementgood first issuehacktoberfestv1-deprecated

Description

Is your feature request related to a problem? Please describe. There are so many warnings coming up while running the tool in the local dev environment.

Describe the solution you'd like Fix the warnings

Join the Discord Server for further discussions. Server Link: https://discord.gg/HHMs7Eg

Contributor guide

Tech stack
javascriptnodejshtmlcss
Domain
frontend
Issue type
refactor
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.
under 1 hour
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
Basic JavaScriptESLint knowledgenpm/yarn basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
First, clone the repository and install dependencies with npm install. Then run the ESLint command to see the current warnings (likely via npm run lint). Identify the specific warnings from the screenshot or by running lint. The ESLint configuration is probably in .eslintrc or package.json. Fix each warning by adjusting the code according to ESLint rules. Common fixes include adding missing semicolons, correcting indentation, or removing unused variables. Check if there are any linked pull requests or comments from the assignee about progress. If the warnings persist, consult the Discord server linked in the issue for guidance.