-
-
Notifications
You must be signed in to change notification settings - Fork 603
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: upgrade all dependencies, devDependencies #290
Conversation
package.json
Outdated
"eslint-plugin-node": "^5.1.0", | ||
"flow-bin": "^0.49.1", | ||
"eslint-plugin-node": "^6.0.1", | ||
"flow-bin": "^0.66.0", |
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.
You can remove flow-bin
, it's not used anymore
I think you should rebase from |
package.json
Outdated
@@ -123,7 +123,6 @@ | |||
"cz-customizable": "^5.2.0", | |||
"eslint": "^4.2.0", | |||
"eslint-plugin-node": "^6.0.1", | |||
"flow-bin": "^0.66.0", | |||
"flow-remove-types": "^1.2.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.
Sorry to bother again! Just noticed that we can also remove flow-remove-types
!
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.
Ah! No worries. I just ran npm-check
to check for all unused deps and this is the list of unused deps returned in output:
Can you please confirm which ones to keep/remove?
global
recast
uglifyjs-webpack-plugin
@commitlint/cli
@commitlint/prompt-cli
commitizen
conventional-changelog-lint-config-cz
husky
lint-staged
schema-utils
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 one here
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've cleaned flow-bin
, flow-remove-types
as suggested by @ematipico
Also, updated PR description.
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.
Gotta double check the colors thing, do not update yargs, as there's a security volun on the new version.
c1824f1
to
c4ff478
Compare
@ev1stensberg Reverted back to |
31706f4
to
fbc645d
Compare
bin/webpack.js
Outdated
@@ -318,7 +318,7 @@ | |||
}); | |||
|
|||
if (typeof outputOptions.colors === "undefined") | |||
outputOptions.colors = require("supports-color"); | |||
outputOptions.colors = require("supports-color").stdout; |
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.
Anything changed in a newer version?
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.
Doesn't look like anything changed relevant to us other than the API.
There are no changelogs or release notes but you can take a look at this PR #64.
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.
Remove the stdout and you're good. Doesn't work with it
bin/webpack.js
Outdated
@@ -318,7 +318,7 @@ | |||
}); | |||
|
|||
if (typeof outputOptions.colors === "undefined") | |||
outputOptions.colors = require("supports-color"); | |||
outputOptions.colors = require("supports-color").stdout; |
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.
Remove the stdout and you're good. Doesn't work with it
@dhruvdutt Thanks for your update. I labeled the Pull Request so reviewers will review it again. @ev1stensberg Please review the new changes. |
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.
Need another reviewer to lgtm this, it's a big change, might break some parts we don't test
rebase against master |
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
Already rebased. All tests basically fail with this error: (Check expected and contain values) It should match but it doesn't. Most likely there's some weird issue that ANSI terminal color codes aren't parsed due to some reason when the tests run. Check the screenshot below. Printing console.log(stdout[5]);
console.log(stdout); However this doesn't happen when we add require("supports-color").stdout There are no changelogs for Currently added |
Conflicts |
@ev1stensberg Resolved. 💯 |
bin/process-options.js
Outdated
@@ -37,7 +37,7 @@ module.exports = function processOptions(yargs, argv) { | |||
}); | |||
|
|||
if (typeof outputOptions.colors === "undefined") | |||
outputOptions.colors = require("supports-color"); | |||
outputOptions.colors = require("supports-color").stdout; |
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 stdout here
bin/webpack.js
Outdated
@@ -318,7 +318,7 @@ | |||
}); | |||
|
|||
if (typeof outputOptions.colors === "undefined") | |||
outputOptions.colors = require("supports-color"); | |||
outputOptions.colors = require("supports-color").stdout; |
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 stdout here
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.
Removing this breaks the tests. Did you read my above comment?
Do we want the tests to fail?
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 want colors to work as intended. If the tests are failing you gotta fix em 👩💻✌️
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.
Coolio. So, in that case we can use something like ansi-parser to parse stdout
inside tests. WDYT?
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.
Remove the stdout and lemme have a look
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.
Done. You're up captain. 💂♂️
bin/webpack.js
Outdated
@@ -80,7 +80,7 @@ | |||
type: "boolean", | |||
alias: "colors", | |||
default: function supportsColor() { | |||
return require("supports-color"); | |||
return require("supports-color").stdout; |
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 stdout
What kind of change does this PR introduce?
Feature/Upgrade
Did you add tests for your changes?
Updated migrate snapshot (031b798)
Summary
yargs
*. 🚀supports-color
usage to resolve breaking changesflow-bin
,flow-remove-types
*We will need to doublecheck on
yargs
changelog for breaking changes in version 10.0.0 and 11.0.0Does this PR introduce a breaking change?
No