jsx-eslint/eslint-plugin-react

[Bug]: react/prop-types error detected on linux but won't on windows

Open

#3702 opened on Mar 6, 2024

View on GitHub
 (6 comments) (0 reactions) (0 assignees)JavaScript (8,630 stars) (2,797 forks)batch import
bughelp wanted

Description

Is there an existing issue for this?

  • I have searched the existing issues and my issue is unique
  • My issue appears in the command-line and not only in the text editor

Description Overview

windows detect react/prop-types error for only client component, and linux detect error from server and client component

windows: image

linux: image

I am develop nextjs 13 app with server component & client component without defining propTypes for both, but npm run lint only the detect error for client component. I cloned same code base on Fedora 38 and unlike window npm run lint detect error for both client and server component

npm run lint npx next build

Expected Behavior

It should be output same error both windows or linux, since many developers use windows as dev env and linux as production.

windows: image

linux: image

eslint-plugin-react version

v7.33.2

eslint version

v8

node version

v18.19.1

Contributor guide

Tech stack
javascriptreactnodejs
Domain
toolingdeveloper experience
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of ESLint pluginsFamiliarity with Node.js file system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate why react/prop types rule behaves differently on Windows and Linux. Check the rule implementation in eslint plugin react, focusing on how it resolves file paths and determines server vs client components in Next.js. Examine ESLint configuration differences, line endings, and path separators. Look at the comments on the issue for any additional clues.