Thanks for this!

For posterity, would you mind elaborating on the issues you hit, in case some other frameworks face similar problems?

Ah sorry I had missed your message, and I've since then forgotten the details of the problems I ran into.

From vague memory, I had two problems, with the javascript tooling stack rather than the code itself:

1. in the package.json dependencies, using link:... for the shared libraries didn't work for some reason (the wasm would fail loading at runtime in the browser). Using file:... instead worked:

    "shared": "file:../shared/pkg",
    "shared_types": "file:../shared_types/generated/typescript",

2. In the vite.config.ts file (default file provided with the official solidjs/vite template), I needed to explicitly tell vite to not optimize the shared wasm dependency:

export default defineConfig({
  plugins: [solid()],
  optimizeDeps: {
    exclude: ["shared"],
  },
});

Otherwise, if I remember right, the wasm would have missing symbols when called at runtime.