Closed sysmat closed 10 months ago
@sysmat this issue is correlated to #48
The only fix for you now is to rollback vitest to 0.34.2 or use Node 18.18.2. In Node 18.19.0 they backported a breaking change in module resolution.
Note that this seems to be resolved when using the latest version of vitest (which is 1.2.0 at the time of this writing).
I moved from throwing an error to issuing a warning. I also updated vite-plugin-solid so it should do most of the required testing config for you (except for globals, coverage, watch, etc.).