Skip to content
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

Merged
merged 3 commits into from
May 19, 2023
Merged

chore(deps): upgrade all npm dependencies #266

merged 3 commits into from
May 19, 2023

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented May 19, 2023

No description provided.

Comment on lines +88 to 89
// @ts-expect-error TODO: decipher why this produces an error
if (range.test(name) && maxSV?.compare(name) !== 1) {
Copy link
Contributor Author

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) {

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// @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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// @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.

@aduh95 aduh95 enabled auto-merge (squash) May 19, 2023 09:34
@aduh95 aduh95 merged commit 863e0e0 into main May 19, 2023
@aduh95 aduh95 deleted the upgrade-deps branch May 19, 2023 09:37
Comment on lines +88 to 89
// @ts-expect-error TODO: decipher why this produces an error
if (range.test(name) && maxSV?.compare(name) !== 1) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// @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?

Comment on lines +1 to +4
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';
Copy link
Member

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.

Copy link
Contributor Author

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.

Copy link
Member

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.

Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants