-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
v1-ssr-mst-aptd-gcms-lcz-sty update deps #27
v1-ssr-mst-aptd-gcms-lcz-sty update deps #27
Conversation
…[email protected] packages (devDeps, non critical)
…[email protected], [email protected] packages (react packages)
…[email protected], [email protected] packages (jest packages + non-critical)
[GitHub Actions] |
1 similar comment
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
5f2c7bd
to
7c9c32e
Compare
[GitHub Actions] |
Rewrote history to rollback to Replaying all packages updates one by one (I believe next-with-apollo may not be the only one breaking SSR) |
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
[GitHub Actions] |
…it installs @apollo/react-ssr which requires to change the current configuration - See lfades/next-with-apollo#126 (comment))
[GitHub Actions] |
[GitHub Actions] |
…/react-ssr and update HOC for GraphQL data fetching - See lfades/next-with-apollo#126 (comment) (tested locally and it DOES fix the SSR issue!)
[GitHub Actions] |
Confirming SSR works fine now https://nrn-v1-ssr-mst-aptd-gcms-lcz-sty-c1-mosund99m.now.sh/ |
[GitHub Actions] |
…tstrap NavLink is an actual link and not just a decorator)
… directly, or link won't work if JS is disabled)
[GitHub Actions] |
[GitHub Actions] |
Goal
Updating all deps that can safely be updated.
Regressions
[email protected]
is being used.Fixed through #27 (comment)
Warnings
Fixed by
[email protected]
See https://fb.me/setstate-in-render
Issue seems to come from react-i18next useTranslation hook(wrong assumption)Or i18next when emiting something(wrong assumption)Hard to tell. It's just a warning with no incidence. It just highlights an existing issue that weren't obvious before. => Was due to
react-apollo
Dependencies not updated
.
after?
inthis.readonlyCookies?.[USER_LS_KEY];
- Zeit support has been contacted, no ETA fix, won't wait for a fix.