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

[fauzanashari]

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:

linux:

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:

linux:

eslint-plugin-react version

v7.33.2

eslint version

v8

node version

v18.19.1

[ljharb]

Can you confirm on the command line that this behavior occurs (vscode isn’t the source of truth), and that both envs have the same deps at the same versions installed on disk?

[fauzanashari]

Can you confirm on the command line that this behavior occurs (vscode isn’t the source of truth), and that both envs have the same deps at the same versions installed on disk?

linux

windows

both files location on ./src/app/role-permission/ubah/[id]/page.jsx and you can see in windows it doesn't even throw an error from these file

[erlanggaht]

The bug is in all Linux versions, mas ?

[ljharb]

@fauzanashari what is [id]? is it literal square brackets (which might break many file system tools), or is it a placeholder for something else?

[fauzanashari]

@fauzanashari what is [id]? is it literal square brackets (which might break many file system tools), or is it a placeholder for something else?

yes nextjs this is nextjs convention to create dynamic slug url https://nextjs.org/docs/app/building-your-application/routing/dynamic-routes

[ljharb]

interesting - i wonder if that's the issue. I'll try to create a test case to rule that out.