sahat/hackathon-starter

Re-introduce lint-staged

Open

#1612 opened on Apr 11, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (35,217 stars) (8,171 forks)batch import
good first issuehelp wanted

Description

Re-introduced lint-staged to reduce commit friction by reducing the number of files that are being linted.

Contributor guide

Tech stack
javascriptnodejs
Domain
developer experiencetooling
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.jsGitlint staged concept
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
The issue asks to re introduce lint staged to reduce commit friction. The contributor should check if lint staged was previously removed and why. Then install lint staged via npm, configure it in package.json or .lintstagedrc, and integrate with husky or similar pre commit hooks. Ensure the configuration lints only relevant files (e.g., *.js, *.css). Test by making a commit; the hook should run only on staged files. No existing PR or comments were found.