-
Notifications
You must be signed in to change notification settings - Fork 173
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
chore(deps): upgrade all npm dependencies #266
Conversation
// @ts-expect-error TODO: decipher why this produces an error | ||
if (range.test(name) && maxSV?.compare(name) !== 1) { |
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.
No idea why this code generates the following error:
error TS2339: Property 'compare' does not exist on type 'never'.
88 if (range.test(name) && maxSV?.compare(name) !== 1) {
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.
// @ts-expect-error TODO: decipher why this produces an error | |
if (range.test(name) && maxSV?.compare(name) !== 1) { | |
if (range.test(name) && maxSV && maxSV.compare(name) !== 1) { |
This works so potentially a TypeScript bug?
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.
// @ts-expect-error TODO: decipher why this produces an error | |
if (range.test(name) && maxSV?.compare(name) !== 1) { | |
if (range.test(name) && (maxSV as semver.SemVer | undefined)?.compare(name) !== 1) { |
This also don't trigger the error, so definitely a TS bug, I guess we just have to wait for them to fix it.
// @ts-expect-error TODO: decipher why this produces an error | ||
if (range.test(name) && maxSV?.compare(name) !== 1) { |
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.
// @ts-expect-error TODO: decipher why this produces an error | |
if (range.test(name) && maxSV?.compare(name) !== 1) { | |
if (range.test(name) && maxSV && maxSV.compare(name) !== 1) { |
This works so potentially a TypeScript bug?
import {describe, beforeEach, it, expect} from '@jest/globals'; | ||
import {Filename, ppath, xfs, npath} from '@yarnpkg/fslib'; | ||
import {delimiter} from 'path'; | ||
import {delimiter} from 'node:path'; | ||
import process from 'node:process'; |
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.
These changes shouldn't be necessary, these are all global by default.
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.
It's indeed not necessary, more like a personal preference.
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.
Sure, but they don't really belong in a chore(deps): upgrade all npm dependencies
commit.
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.
Fair enough, I thought at first it was necessary for this PR of the output of https://github.com/nodejs/corepack/actions/runs/5022431482/jobs/9005884303, turns out it was not and I left them because I liked them. My bad.
No description provided.