Option to specify WASM binary path

[gbl08ma]

The library appears to employ some logic to deduce where tcpip.wasm should be present, but this doesn't work in my case (possibly because of the way Vite does things). It would be nice to have an option in the NetworkStackOptions passed to createStack which would allow for setting a custom path to the wasm file, much like v86 does with its wasm file.

[gregnr]

Sure, we can make this configurable. For the case of Vite, I was able to get this to work by excluding tcpip from dep optimization:

import { defineConfig } from 'vite';

export default defineConfig({
  ...
  optimizeDeps: {
    exclude: ['tcpip'],
  },
});

Unfortunately this seems to be the case for all WASM libs loaded in Vite via standard new URL('/lib.wasm', import.meta.url) syntax: vitejs/vite#8427