Use URL to get path to wasm asset

[freaz]

As follow up to findings from POD and how Webpack resolves paths to assets, this changes require.resolve to URL, to get path to core wasm asset.

It should work better with bundlers, but keep working the same when used without.

I also moved it to common, as it feels more generic, then just specific to Node.js. Even though it can't be used in CF worker.

[TheEdward162]

Did you test this with the cloudflare example? It errors for me with Could not resolve "node:fs/promises" when I run wrangler dev or wrangler publish due to the wasm.js file being reachable from common.

[freaz]

Thanks. I did not try it. Also reason why it was in Node in the first place. I now kept just the function to get path to was in common, so every platform loads it as it suites it.

[TheEdward162]

It's a shame we can't utilize the corePath function in cloudflare/esm import too, but that's just a dream.

[freaz]

I guess we could use async import or require.resolve with it, but not sure if it is better.