Update tooling #74
Open
Update tooling #74
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Open
|
Hi, I can re-checkout this branch & re-update deps along with other checks to see if this branch is still good to go. Would you have a couple of hours to spend on this in the next weeks? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update all dev dependencies to latest versions.
Non trivial changes are:
Unused npm scripts were removed.
Note that all tooling changes are in 1d00113. Other commits are mostly changes auto-generated by new tooling versions, except a couple of typescript code changes in repercussion of typescript update from
^2.0.0to^4.0.0.At this point, tests are failing without #73 : Typescript output might have changed a bit, thus really triggering bug expected in #58