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 some deps #2542

Merged
merged 9 commits into from Apr 29, 2020
Merged

chore(deps): upgrade some deps #2542

merged 9 commits into from Apr 29, 2020

Conversation

hiroppy
Copy link
Member

@hiroppy hiroppy commented Apr 28, 2020

  • This is a bugfix
  • This is a feature
  • This is a code refactor
  • This is a test update
  • This is a docs update
  • This is a metadata update

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

@codecov
Copy link

codecov bot commented Apr 28, 2020

Codecov Report

Merging #2542 into v4 will decrease coverage by 0.40%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            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     
Impacted Files Coverage Δ
lib/utils/createConfig.js 96.26% <ø> (-0.20%) ⬇️
client-src/default/overlay.js 97.01% <100.00%> (+0.04%) ⬆️
lib/Server.js 96.35% <100.00%> (-0.45%) ⬇️
lib/servers/SockJSServer.js 93.75% <100.00%> (ø)
lib/utils/addEntries.js 100.00% <100.00%> (ø)
lib/utils/runOpen.js 100.00% <100.00%> (ø)
lib/utils/updateCompiler.js 100.00% <100.00%> (ø)
client-src/default/utils/reloadApp.js 86.95% <0.00%> (-13.05%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4e9b3db...fa6b9ca. Read the comment docs.

@hiroppy
Copy link
Member Author

hiroppy commented Apr 28, 2020

internal-ip doesn't support Node@8. I'll delete it.

    /home/vsts/work/1/s/node_modules/internal-ip/index.js:35
      } catch {}

@hiroppy
Copy link
Member Author

hiroppy commented Apr 28, 2020

puppeteer is breaking when using Node@14 so I downgraded from v3 to v2.
FYI: puppeteer/puppeteer#5719

@hiroppy
Copy link
Member Author

hiroppy commented Apr 28, 2020

CI is green.

package.json Outdated
"yargs": "12.0.5"
"webpack-log": "^3.0.1",
"ws": "^7.2.5",
"yargs": "^15.3.1"
Copy link
Member

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",
Copy link
Member

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)

Copy link
Member

@alexander-akait alexander-akait left a 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

@hiroppy
Copy link
Member Author

hiroppy commented Apr 28, 2020

@evilebottnawi PTAL

Copy link
Member

@alexander-akait alexander-akait left a 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",
Copy link
Member

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

@hiroppy
Copy link
Member Author

hiroppy commented Apr 28, 2020

@evilebottnawi updated

"ws": "^6.2.1",
"yargs": "12.0.5"
"webpack-log": "^3.0.1",
"ws": "^7.2.5",
Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Collaborator

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' }`
@alexander-akait
Copy link
Member

@hiroppy Why do you use feature/upgrade-deps branch for hot: true?

@alexander-akait
Copy link
Member

No we can't squash this PR

@hiroppy
Copy link
Member Author

hiroppy commented Apr 28, 2020

@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 rebase and merge when this branch is merged to v4.

"type": "boolean"
},
{
"enum": ["only"]
Copy link
Collaborator

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?

Copy link
Member

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

Copy link
Member

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

Copy link
Member

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
@hiroppy
Copy link
Member Author

hiroppy commented Apr 29, 2020

NOTE: Must select rebase and merge when merging.

@alexander-akait alexander-akait merged commit 4fc5ecd into v4 Apr 29, 2020
@alexander-akait
Copy link
Member

alexander-akait commented Apr 29, 2020

@hiroppy @Loonride good job, let's remove inline and live client

I remember we wanted to change the structure of client directory, somebody can take care too!

@hiroppy
Copy link
Member Author

hiroppy commented Apr 29, 2020

@evilebottnawi This PR commit was put together...😞 why did you select squash and merge...? we can't generate the true changelog..

@alexander-akait alexander-akait deleted the feature/upgrade-deps branch April 30, 2020 08:56
@alexander-akait
Copy link
Member

@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

alexander-akait pushed a commit that referenced this pull request May 8, 2020
* 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
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.

None yet

3 participants