Investigate using Vitest in combination with Effect as testing setup

[schickling]

I really like the Vite-backed "HMR" system applied to testing workflows as demonstrated here: https://twitter.com/antfu7/status/1468233216939245579

We should investigate how Vitest can be used in Effect projects.

I'm currently running in the following problems:

• Effect should use fully qualified import paths (e.g. import {} from './some-file.js' instead of import {} from './some-file'). Possibly related to Errors from running Vite nodejs tests vitest-dev/vitest#202
  
• Effect currently relies on running tsc for the sake of applying the tsc-plugin. This massively slows down the refresh cycle.

[mikearnaldi]

Effect currently relies on running tsc for the sake of applying the tsc-plugin. This massively slows down the refresh cycle.

Effect doesn't rely on any compiler plugin, if you want features like tracing and optimization the compiler plugin is a non avoidable requirement given that the functionality relies on knowledge of the types but if you don't care about those features you can compile using any tool.

Effect should use fully qualified import paths

It is a major change that is already in the workings for the next release and will be addresses in the compiler extension, probably won't happen in current unless we manage to find a quick solution

[mikearnaldi]

Resolved in recent releases