`@vitest/web-worker` didn't transform `.wasm?url` in worker import about vitest HOT 11 CLOSED

@vitest/web-worker is only a web worker emulation on node runtime, so it doesn't deal with Vite client ?url convention.

You might have a better chance running that with Vitest browser mode instead https://vitest.dev/guide/browser/

If you really need to test wasm binding on non browser mode Vitest, then it might require some restructuring like I suggested previously in a different issue #5704 (comment)

from vitest.

Vite and Vitest resolve the same value of import, but as I said in the previous comment, the environment where it runs is different, so how you use the value depends on your use case.

In your code you pass the value to fetch - in the browser, it resolves the URL relative to the server origin (http://localhost + /gsa.wasm), but on the server fetch doesn't have this information and it requires a full URL :) (just /gsa.wasm is not a valid URL)

from vitest.

I search the issue previously, seems the browser mode won't collect the coverage for the worker?

from vitest.

Right, I think you're referring this issue and coverage is not supported #4899 (comment)

from vitest.

I created a hack to import the wasm in the normal test file and mock it to the worker, please see Zxilly/go-size-analyzer@45149d9

from vitest.

But I don't understand why in this case worker.ts is still not covered by coverage.

from vitest.

After switch to v8 coverage provider things got resolved.

from vitest.

?url actually resolves the file as an absolute pathname (this is Vite feature, not Vitest). To make it a valid file you still need an origin like http://localhost - but since in Node.js there is no origin, you should probably resolve it to a file:// yourself somehow.

Closing this as it's working as expected.

from vitest.

As https://vitest.dev/guide/why.html suggested

A test runner that uses the same configuration of your App (through ), sharing a common transformation pipeline during dev, build, and test time.

I think keep this behavior same between the vite and vitest is meaningful.

from vitest.

This is why we keep the behaviour :)

Vite and Vitest resolve the same value of import, but as I said in the previous comment, the environment where it runs is different, so how you use the value depends on your use case.

from vitest.

I understand that, maybe need to setup a transformer for node environment. Thanks.

from vitest.