refactor: use .ts sources and vitest #37
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.
I wrote this library using
.js
files and TypeScript types in JSDoc comments, to see how far I could go that way.It works pretty well and lets you run code with Node directly, as well as using Node's built-in test runner.
There are a few downsides though:
.ts
files.So now that I’ve shown myself that it’s doable and not too painful without a build step and transpilation shenanigans involved, as a matter of personal preference I’m switching to
.ts
sources and Vitest.One small win: using Vitest unlocks running tests on Node 18, since we no longer depend on
node:test
'ssuite
function (not available in Node 18).