build: update dev deps

[RebeccaStevens]

fix #236

It looks like a lot but most of it is just lining updates.
Look at just the first commit to see what's actually changed.

[RebeccaStevens]

Looks like the testing update I made doesn't work in node 16.
How would you like to resolve this? Drop support for node 16? or should I see if I can get it working.

[vitaly-t]

Looks like the testing update I made doesn't work in node 16. How would you like to resolve this? Drop support for node 16? or should I see if I can get it working.

What's the minimum version that does work? is it v18? Technically, this is just for testing and assembling a release, it is not a functional limitation, so I am quite ok to up min node version to 18, if needed ;)

[vitaly-t]

Other than that, as I went through the scope of changes - that looks huge! I'm particularly intrigued by the addition of type everywhere. Can you tell me, please, why it became needed?

[RebeccaStevens]

Looks like the testing update I made doesn't work in node 16. How would you like to resolve this? Drop support for node 16? or should I see if I can get it working.

What's the minimum version that does work? is it v18? Technically, this is just for testing and assembling a release, it is not a functional limitation, so I am quite ok to up min node version to 18, if needed ;)

Looks like v18 works

[vitaly-t]

Couple things - comments in JSON, plus the Node version.

[RebeccaStevens]

addition of type everywhere. Can you tell me, please, why it became needed?

First thing to note, I replaced ts-node with tsx.
When running the tests, tsx will strip out all the imports/exports marked as type imports/exports. If they weren't stripped out we'd get a runtime error when trying to import the type at runtime.
All though it's possible to not have to explicitly mark each type import, and continue to run things as we did with ts-node, explicitly marking them comes with additional improvements.
Additionally, I setup the the eslint rule @typescript-eslint/consistent-type-imports and '@typescript-eslint/no-import-type-side-effects to enforce this (they have fixers so you don't need to worry about explicitly adding type when writing code).

[vitaly-t]

addition of type everywhere. Can you tell me, please, why it became needed?

First thing to note, I replaced ts-node with tsx. When running the tests, tsx will strip out all the imports/exports marked as type imports/exports. If they weren't stripped out we'd get a runtime error when trying to import the type at runtime. All though it's possible to not have to explicitly mark each type import, and continue to run things as we did with ts-node, explicitly marking them comes with additional improvements. Additionally, I setup the the eslint rule @typescript-eslint/consistent-type-imports and '@typescript-eslint/no-import-type-side-effects to enforce this (they have fixers so you don't need to worry about explicitly adding type when writing code).

Thank you for the clarification! 🤗

[vitaly-t]

@RebeccaStevens

LGTM, thank you for this incredible work, I would not have been able to make it myself!

Leaving it for you to merge whenever you think it is ready 😉