-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Framework: update to react 16 (take three) #19723
Conversation
Note that |
@kwight |
fe665b1
to
beed2bb
Compare
This had become quite out of date. Rebased, |
beed2bb
to
51e8ccb
Compare
Rebased again, sorry. |
51e8ccb
to
d093ff6
Compare
Ack, will verify 2.1.1. |
|
I'm basing this off the ssr fix now |
d093ff6
to
66e321e
Compare
|
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 done the following smoke testing and encountered no issues 🎉
- local dev
- docker. note: ssr will be broken unless secrets.json is configured.
- there should be no reference to React < 16 within our shrinkwrap
For SSR I see /themes
is correct (logged in and logged out) if config/secrets.json
is included. Otherwise I see the following message and the issue pictured here.
Disabling server-side user-bootstrapping because of a missing secrets.json
@@ -106,7 +106,7 @@ | |||
"ms": "0.7.1", | |||
"name-all-modules-plugin": "1.0.1", | |||
"node-sass": "4.5.3", | |||
"notifications-panel": "1.2.7", | |||
"notifications-panel": "2.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.
Should we get the current 2.1.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.
also React 16.2!
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.
Love those <>Fragments</>
🎉
Running tests now produces far fewer warnings, which is nice. Now we have a new annoyance:
Relevant conversation seems to be happening here: jestjs/jest#4545. Just a warning, so nothing blocking and we can ship a fix later. |
0bae1d6
to
0349330
Compare
package.json
Outdated
@@ -277,7 +277,7 @@ | |||
"prettier": "github:automattic/calypso-prettier#717e62ee", | |||
"pretty-bytes": "4.0.2", | |||
"react-codemod": "reactjs/react-codemod", | |||
"react-test-renderer": "15.6.2", | |||
"react-test-renderer": "16.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.
Also bump to 16.2.0?
I've had to bump back down to 2.0 due to issues with |
My bad. Context: #19698 To fix, we can:
|
Am I right in thinking that can all happen after this PR lands? |
fd8be57
to
fc1dbc3
Compare
after upgrading a few packages (and then redowngrading notif-panel), i'll do another smoke test and then ask for an E2E from flow-patrol |
Oh, absolutely! Sry for not having been clear 😄 |
As pretty much anything that doesn't make Calypso go up in 🔥s at this point 😄 |
E2E tests passed |
Everyone knows the third time is the charm.
to do:
To Test and Verify
secrets.json
is configured.