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 some deps #2542
Conversation
Codecov Report
@@ Coverage Diff @@
## v4 #2542 +/- ##
==========================================
- Coverage 93.77% 93.36% -0.41%
==========================================
Files 34 34
Lines 1334 1327 -7
Branches 381 375 -6
==========================================
- Hits 1251 1239 -12
- Misses 81 85 +4
- Partials 2 3 +1
Continue to review full report at Codecov.
|
internal-ip doesn't support Node@8. I'll delete it.
|
c1ef6a3
to
6d5b6b1
Compare
6d5b6b1
to
e8f54c4
Compare
puppeteer is breaking when using Node@14 so I downgraded from v3 to v2. |
CI is green. |
package.json
Outdated
"yargs": "12.0.5" | ||
"webpack-log": "^3.0.1", | ||
"ws": "^7.2.5", | ||
"yargs": "^15.3.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.
Please do no touch yargs, it can potential break CLI
package.json
Outdated
"serve-index": "^1.9.1", | ||
"sockjs": "0.3.20", | ||
"sockjs-client": "1.4.0", | ||
"spdy": "^4.0.2", | ||
"strip-ansi": "^3.0.1", | ||
"supports-color": "^6.1.0", | ||
"strip-ansi": "^6.0.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.
We can't do it, we will break client on old browsers, we need setup babel on our client and then do update (let's do backport it from previously next)
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.
Good job, two things we should not update in this PR
@evilebottnawi PTAL |
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.
Seems one mistake
package.json
Outdated
@@ -36,39 +36,40 @@ | |||
"release": "standard-version" | |||
}, | |||
"dependencies": { | |||
"@jest/test-sequencer": "^25.4.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.
I think we should move it to devDependencies
3f07520
to
39d0213
Compare
@evilebottnawi updated |
"ws": "^6.2.1", | ||
"yargs": "12.0.5" | ||
"webpack-log": "^3.0.1", | ||
"ws": "^7.2.5", |
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.
/cc @Loonride hope we don't breaking anything, can you 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.
This module supports only Node.js so not breaking 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.
based on ws changelog it should be fine
BREAKING CHANGE: the `hot` option is `true` by default, the `hotOnly` option was removed in favor `{ hot: 'only' }`
@hiroppy Why do you use |
No we can't squash this PR |
@evilebottnawi I said you yesterday to merge this branch early as it will be the basis for all our work. The package must be up to date to do all the work because these updated packages are too huge suck as Jest. Yes, we should select |
"type": "boolean" | ||
}, | ||
{ | ||
"enum": ["only"] |
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 not sure I like this change to the hot option because webpack core CLI also has --hot
boolean flag (https://webpack.js.org/api/cli/) and I don't think it's great for usage of a flag of the same name to diverge. This will be annoying to deal with on the webpack-cli serve
side, since we parse the webpack flags, then pass any unknown flags along to the dev server. Thoughts?
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.
@Loonride we should implement hot: only
on webpack-cli side too
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 main problem is that we already have a lot of options and setting up everything is terribly complicated and redundant, we must simplify everything as much as possible
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.
And in some edge cases it is normal what package have same arguments but with many values
BREAKING CHANGE: `lazy` and `filename` options was removed
NOTE: Must select |
@evilebottnawi This PR commit was put together...😞 why did you select squash and merge...? we can't generate the true changelog.. |
@hiroppy Oh, my mistake, anyway I want to put more information to CHANGELOG for new major release, don't worry, I will write it before release |
* chore(deps): upgrade deps * style: run prettier * test: update * ci: remove Node@8 * test(cli): add windows support * chore(deps): downgrade puppeteer * chore(deps): downgrade some deps * fix(hot): enable hot option as default (#2546) BREAKING CHANGE: the `hot` option is `true` by default, the `hotOnly` option was removed in favor `{ hot: 'only' }` * fix: remove lazy and filename options (#2544) BREAKING CHANGE: `lazy` and `filename` options was removed
For Bugs and Features; did you add new tests?
N/A
Motivation / Use-Case
Update all deps.
Jest has many breaking changes so I modified mocks and some event loop such as setTimeout.
Breaking Changes
yes
Additional Info
fixes: #2541