Volodymyr Zhdanov

Upd. was able to force esm for most deps using alias and https://github.com/vitest-dev/vitest/pull/1673 But some dependencies can not into esm at all, e.g. styled-components, see ``` ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯...

> @wight554 yes, I also tried this MR agains your repro with no luck. > > > Is there any way I can force preact to be CJS > >...

Upd. was able to fix it by using cjs interop for all 'preact/hooks' (all packages with multiple version) imports and testing library In my case I can fix it on...

> @wight554 cjs interop is the same as using `const mod = require('path')`, so I don't see why you really want to use it over simple require in this case....

> Upd. was able to fix it by using cjs interop for all 'preact/hooks' (all packages with multiple version) imports and testing library In my case I can fix it...

Upd. cleanest solution I was able to implement: ``` import { createRequire } from 'module'; const require = createRequire(import.meta.url); alias: [ { find: 'preact/hooks', replacement: require.resolve('preact/hooks'), }, { find: '@testing-library/preact',...

> > would be nicer to see smth like this in vitest itself > > Vitest has both `alias` and `test.alias` config options, what else do you need? How users...

looks good overall, noticed few issues: 1. exclude option seems to be ignored when using instanbul 2. when setting provider to c8 explicitly `vitest run --coverage` skips coverage 3. vitest...

Any blockers for this one?

Ended up using PRIME_NOZZLE from [here ](https://www.reddit.com/r/VORONDesign/comments/qztck1/comment/hlpoxq3) for now. But this option would be much better