chore: update typescript, drop Node v16 compatibility #1836
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
tkurki
force-pushed
the
update-typescript
branch
2 times, most recently
from
a720ca4 to
8072558
Compare
tkurki
force-pushed
the
update-typescript
branch
from
8072558 to
af3ee51
Compare
For some reason we had both rmfr and rimraf. Use just rimraf's latest version.
Don't run tests with 16 any more. For example structuredClone is needed by dev tooling.
tkurki
force-pushed
the
update-typescript
branch
from
556104c to
e5df925
Compare
tkurki
changed the title
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 typescript and related utilities to ts 5.6.x.
Fix related lint & typing errors that came up with the update.
Fix minor bug in setting numerical settings from the UI.
Use path.join instead of concatenation to form the path to module's package.json.
Drop running tests with Node v16, so in effect drop compatibility with it as there is nothing to ensure that. The driver was dev tooling compatibility, so the server proper probably works still with Node 16.