Initial support of vitest benchmark

[zkulbeda]

This separated pr is required to merge into main branch for testing github actions workflow in next coming pr #100. I just copied one of the tests from typescript-runtime-type-benchmark just for demo purposes.

Is benchmarks folder in ./library/src good place for storing benchmarks files?

[netlify]

✅ Deploy Preview for valibot canceled.

Name	Link
🔨 Latest commit	8baa0c0
🔍 Latest deploy log	https://app.netlify.com/sites/valibot/deploys/64e338b66ce73800080afda3

[fabian-hiller]

Thank you very much! The next few days I have to focus on my bachelor thesis. As soon as I find time, I'll get back to you.

[fabian-hiller]

Do you have any idea how we can make the result comparable to the latest version of Valibot, so we can see if changes have a positive or negative impact on the performance?

[fabian-hiller]

We could add the latest version of Valibot as a dev dependency and run the benchmark for both to have a comparison of the codebase to the latest Valibot version.

[zkulbeda]

That's great idea for local testing without pull request! But I should research if adding dev dependency can make a conflict with existing package name or add alias to dependency to avoid collision.

[zkulbeda]

Hi, @fabian-hiller, I added valibot dependency and now it's possible to compare current and latest perfomance in tests. Can you check it?

[fabian-hiller]

Yes, I will try to check it in the next few days.

[fabian-hiller]

Sorry for not coming back to this, but other things had a higher priority. I am also not sure if we really need it, since the basic structure of the library is set and changes will most likely not have a major impact on performance. It is still useful, but other things have a higher priority for me.