Upgrade deps for v2-mst-aptd-gcms-lcz-sty #165
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Similar to #163 but for preset
v2-mst-aptd-gcms-lcz-sty
.Used #163 as base work and added stuff specific to
v2-mst-aptd-gcms-lcz-sty
on top of it.Before upgrade
After upgrade
Non-upgraded deps:
@welldone-software/why-did-you-render
: Alpha version, non-documented changelognow
: Version 20.1.0 doesn't work when deploying. Ticket sent to Vercel and support will take it from there.markdown-to-jsx
: Not stable TS types, WIP in TS error with v7.0.0 - Type error: Module '"../../../node_modules/markdown-to-jsx/dist"' has no exported member 'MarkdownOptions'. Did you mean to use 'import MarkdownOptions from "../../../node_modules/markdown-to-jsx/dist"' instead? quantizor/markdown-to-jsx#332winston
: Size has grown and there is no need to add more bytes to the client-side bundle, since we would love to remove it from the project in the first place.@apollo/react-hooks
and@apollo/react-ssr
New major version, huge breaking changes. Theoretically, we should drop both packages and use@apollo/client
instead. But not only the NPM domain has changed, the packages have been upgraded too and there are multiple breaking changes to take into account. See https://www.apollographql.com/docs/react/migrating/apollo-client-3-migration/#breaking-cache-changes As I don't have the time to thoroughly test this massive upgrade, I won't do it yet.next-with-apollo
: No changelog, no idea what has changed. https://github.com/lfades/next-with-apollo/releases. There seems to be several changes but, same story, no time to test to see if there aren't some edge case regression ATM. https://github.com/lfades/next-with-apollo/pulls?q=is%3Apr+sort%3Aupdated-desc+is%3Amerged