feat: allow running the tests with vitest

[C0ZEN]

ℹ️ I suggest rebasing the 3 commits instead of squashing them to keep a clean history.

Closes #54

[C0ZEN]

@koliveira15 👀

[Bullfrog1234]

I suggest that this is not a coverage at a app level but at each project level. My code comments show where that would need to change.

Will do an update if not fixed in 4 weeks as I am going to be not able to do until I take Christmas leave.

Overall I like the idea just not the complete implementation. @C0ZEN thanks for the idea.

[C0ZEN]

I made the suggested by @Bullfrog1234 regarding how to handle each libs and apps for the coverage configuration.
It's easier, transparent for the consumers and for sustainable in the future now.

The executor used will be detected, and based on this, the coverage directory path will change to make this project compatible with a runner using vite.

[Bullfrog1234]

Looks good and my opinion can be merged.

@koliveira15 over to you to merge.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 7c738de. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 3 targets

• nx affected -t test --configuration=ci
• nx affected -t build
• nx affected -t lint

---

Sent with 💌 from NxCloud.

[C0ZEN]

@koliveira15 done

[C0ZEN]

BTW, the nx-cloud agent seems not to be triggered again, the lint failure is obsolete, and the commit hash used is an old one.

[koliveira15]

BTW, the nx-cloud agent seems not to be triggered again, the lint failure is obsolete, and the commit hash used is an old one.

I believe that's because you're a first time contributor & using a fork. should be good now

[koliveira15]

@C0ZEN thank you very much for this contribution! ❤️ I plan on refactoring the utils.ts file into smaller, manageable chunks while also improving the architecture to easily allow more test runners in the future.