-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: add missing peer dependencies #9744
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Ensure all transitive peer dependencies are properly listed. This fixes peer-requirements warnings thrown by yarn.
Thanks for the PR, @ethanwu10! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
☁️ Nx Cloud ReportCI is running/has finished running commands for commit dd06088. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
Any update? FYI @JoshuaKGoldberg |
@rtritto The issue has not been marked as accepting PRs. Please do not ping on issues or tag maintainers in comments. |
I have this warnings after p4ee77 → ✓ @typescript-eslint/parser@npm:8.6.0 [3223e] doesn't provide @types/supports-color to debug@npm:4.3.6 [1ff4b]
p42ec1 → ✓ @typescript-eslint/parser@npm:8.6.0 [3223e] doesn't provide supports-color to debug@npm:4.3.6 [1ff4b]
p5cc2b → ✓ @typescript-eslint/type-utils@npm:8.6.0 [8a609] doesn't provide @types/eslint to @typescript-eslint/utils@npm:8.6.0 [7f592] and 1 other dependency
p0f521 → ✓ @typescript-eslint/type-utils@npm:8.6.0 [8a609] doesn't provide @types/supports-color to debug@npm:4.3.6 [1ff4b]
p6eab7 → ✘ @typescript-eslint/type-utils@npm:8.6.0 [8a609] doesn't provide eslint to @typescript-eslint/utils@npm:8.6.0 [7f592] and 1 other dependency
p31167 → ✓ @typescript-eslint/type-utils@npm:8.6.0 [8a609] doesn't provide supports-color to debug@npm:4.3.6 [1ff4b]
pa4871 → ✓ @typescript-eslint/typescript-estree@npm:8.6.0 [346c1] doesn't provide @types/supports-color to debug@npm:4.3.6 [1ff4b]
p66f84 → ✓ @typescript-eslint/typescript-estree@npm:8.6.0 [346c1] doesn't provide supports-color to debug@npm:4.3.6 [1ff4b]
p67afe → ✓ @typescript-eslint/typescript-estree@npm:8.6.0 [7f592] doesn't provide @types/supports-color to debug@npm:4.3.6 [1ff4b]
p1b301 → ✓ @typescript-eslint/typescript-estree@npm:8.6.0 [7f592] doesn't provide supports-color to debug@npm:4.3.6 [1ff4b]
pf4e07 → ✓ @typescript-eslint/utils@npm:8.6.0 [7f592] doesn't provide @types/typescript to @typescript-eslint/typescript-estree@npm:8.6.0 [346c1] and 1 other dependency
pb85fd → ✘ @typescript-eslint/utils@npm:8.6.0 [7f592] doesn't provide typescript to @typescript-eslint/typescript-estree@npm:8.6.0 [346c1] and 1 other dependency
pa9c59 → ✓ @typescript-eslint/utils@npm:8.6.0 [8a609] doesn't provide @types/typescript to @typescript-eslint/typescript-estree@npm:8.6.0 [346c1] and 1 other dependency
pafe94 → ✘ @typescript-eslint/utils@npm:8.6.0 [8a609] doesn't provide typescript to @typescript-eslint/typescript-estree@npm:8.6.0 [346c1] and 1 other dependency I found a workaround (with yarn berry) to this issue: # .yarnrc.yml
packageExtensions:
"@typescript-eslint/type-utils@*":
dependencies:
eslint: ^8 # don't use v9
"@typescript-eslint/utils@*":
dependencies:
typescript: "*" There is an article written by author of yarn package manager: Implicit Transitive Peer Dependencies |
Also Updated workaround using only # .yarnrc.yml
packageExtensions:
"@typescript-eslint/type-utils@*":
dependencies:
eslint: "*"
"@typescript-eslint/utils@*":
dependencies:
typescript: "*"
typescript-eslint@*:
peerDependencies:
eslint: "*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sending this in, and sorry for the wait!
This seems reasonable & straightforward to me. Just one question on the utils
package's meta.
@@ -78,6 +78,11 @@ | |||
"rimraf": "*", | |||
"typescript": "*" | |||
}, | |||
"peerDependenciesMeta": { | |||
"typescript": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Question] Shouldn't this also be listed in peerDependencies
? Even if listing it in peerDependenciesMeta
implicitly adds it there, it feels odd to me to make that implicit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just copied this from type-utils
(which is where the missing dep for typescript comes from), which also does not list it as an explicit peerdep
typescript-eslint/packages/type-utils/package.json
Lines 64 to 68 in 42d275c
"peerDependenciesMeta": { | |
"typescript": { | |
"optional": true | |
} | |
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ha, nice, so this might be an existing issue in that package then? My vote is to fix in both packages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just came here to say that appearently at least both Yarn and pnpm have opted in the past to have "peerDependenciesMeta
without peerDependencies
" imply a peer dependency on *
. This was done due to some (legacy?) npm behavior regarding peer dependencies, making package authors hesistant to list them. See pnpm/pnpm#2128.
But it's probably a better practice to explicitly list them; and given the age of the referenced issue probably safe enough as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason we used peerDependenciesMeta
without peerDependencies
was because there were versions of npm that did not support peerDependenciesMeta
. This meant that when we used an explicit peerDependencies
then users would be spammed with warnings saying they didn't have TS installed. This was a problem as some big packages included our plugins by default but only used them if the user opted in to TS which caused non-TS users to get spammed with missing peer dep errors.
A this point we could probably also include the explicit peerDependencies
on TS but also there's no harm in not including it and having it inferred to ensure that nobody gets spammed with logs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know if npm
also shares this behavior of peerDependenciesMeta
implying peerDependencies
? From a cursory search of the npm sources it seems to me like it doesn't: https://github.com/npm/cli/blob/75a3f1228865f426d8790be27f1258e501f2c450/workspaces/arborist/lib/node.js#L859-L871
Anyways, what do we think of merging this PR first and moving the discussion about whether or not to list an explicit peerdep to a different issue? We don't need to block fixing users' warnings on figuring out the proper manifest declarations 😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm 👍 on that. If nobody else weighs in with a contrary opinion by our weekly release midday Monday EST then we can just merge as-is.
Now that you mention it, I do like the idea of having one release just adding peerDependenciesMeta
, then a subsequent release adding peerDependencies
on top. Just in case there's some bizarre edge case bug with the latter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙌 Thanks for your patience and working with us!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for this!
PR Checklist
Overview
Ensure all transitive peer dependencies are properly listed. This fixes peer-requirements warnings thrown by yarn.