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.
First of all, don't panic! The diff is 99% in the locks that got updated.
This will be a major bump of core, jest, and cypress.
You can review the flags used in tsconfig.json in the official docs. I also used the node 18 base as an inspiration since we are already saying in the readme we require node 18, which is the current active lts.
We discussed in the past a problem with axios-retry not working with axios. But that was only limited to axios 19.0. I tested that fallback mode actually works with the latest axios and axios-retry.
I didn't spot any problematic changes in the dependencies bumped.
I'm leaving the peerDependencies in jest and cypress as they are because I didn't change how we use those, but I believe we should require the same major as we use in devDependencies for jest and cypress.
This also removes
changesets
because it was forcing on us a release workflow that did not work.Bumps