fix: vitest typecheck

[yamcodes]

Tip

The owner of this PR can publish a preview release by commenting /publish in this PR. Afterwards, anyone can try it out by running pnpm add radashi@pr<PR_NUMBER>.

Summary

Fix Vitest typecheck by (1) updating Vitest (2) enabling typecheck (3) pointing typecheck to the tests tsconfig

All 3 avenues must be applied together, omitting one causes type-d.ts files either to pass blindly (false negatives) or not report at all.

Related issue, if any:

Closes #244

For any code change,

• Related documentation has been updated, if needed
• Related tests have been added or updated, if needed
• Related benchmarks have been added or updated, if needed

Does this PR introduce a breaking change?

No

Bundle impact

Status	File	Size 1	Difference
M	src/array/merge.ts	185	-25 (-12%)

Footnotes

1. Function size includes the import dependencies of the function. ↩

[yamcodes]

After experimenting with Vitest versions, we need at least v2.1.0-beta.6. It seems like the following PR fixed the false negatives: vitest-dev/vitest#6256.

I went with 2.1.1 in the PR, which is the latest. I checked that it does not introduce breaking changes relevant to us. The only breaking change between 2.0.5 and 2.1.1 has to do with Vitest Workspaces which we do not use.

[MarlonPassos-git]

Thanks for the PR, I had seen this issue before but hadn't taken the time to fix it.

I tested it in a codespace, and it seems to work fine now, thanks.

Even though type checking is still in beta (I think that was one of the reasons why it wasn't active), it would be worth validating it in the CI stage.

[MarlonPassos-git]

@yamcodes just one thing, fix the PR title for “fix: vitest typecheck”

[yamcodes]

Thanks, @MarlonPassos-git, I agree. Since we have *.test-d.ts files in the branch, we should make sure they can be used.

If we’re wary to use this feature officially, let’s add a separate script in package.json to typecheck. This way you can at least know if the type tests you write work.

However, to keep things simple, I suggest testing both together.

[aleclarson]

This is great 😄 Thanks a lot, @yamcodes