{package-name}-wasm32-wasi is not generated/installed for wasm build

[dikatok]

Heya,

Recently the team at Turso migrates the wasm binding generation to napi v3 https://github.com/tursodatabase/turso/tree/main/bindings/javascript. I tried building the binding locally and import it from a vite project but keeps getting issue with @tursodatabase/database-wasm32-wasi is not generated in the downstream project's node_modules.

Here is the recap of what I did
rustup target add wasm32-wasip1

In bindings/javascript
npm install --cpu wasm32
npm run build -- --target wasm32-wasip1-threads

In my vite project, in this case using a vanilla template in bindings/javascript/examples/opfs
npm install ../../ --cpu wasm32
npm run build
npm run dev

vite.config.js

import { defineConfig } from "vite";

export default defineConfig({
  define: {
    "process.env.NODE_ENV": JSON.stringify(process.env.NODE_ENV),
  },
  server: {
    fs: {
      allow: ["."],
    },
    headers: {
      "Cross-Origin-Opener-Policy": "same-origin",
      "Cross-Origin-Embedder-Policy": "require-corp",
    },
  },
  optimizeDeps: {
    exclude: ["@tursodatabase/database-wasm32-wasi"],
  },
});

Am I missing something?

[Brooooooklyn]

@dikatok can you try to add "browser": "browser.js" in package.json? https://github.com/napi-rs/package-template-pnpm/blob/main/package.json#L7

[dikatok]

@Brooooooklyn I tried both "browser": "browser.js" and "browser": "./dist/browser.js", @tursodatabase/database-wasm32-wasi is still missing in the vite project node_modules.

Here is ls -lah examples/opfs/node_modules/@tursodatabase's result.

drwxr-xr-x   3 dikatok  staff    96B Aug 21 22:24 .
drwxr-xr-x  20 dikatok  staff   640B Aug 21 22:24 ..
lrwxr-xr-x   1 dikatok  staff    11B Aug 21 22:24 database -> ../../../..

[dikatok]

btw I am not using npm link, only npm install with file path aka npm install ../../ which points to the binding directory.

[dikatok]

@Brooooooklyn do I need to run napi artifacts or something else?

[Brooooooklyn]

@dikatok I understand your issue: you are trying to link a local project to another project, but Vite cannot resolve the correct files.

You can temporarily change the "browser": "turso.wasi-browser.js" in https://github.com/tursodatabase/turso/blob/main/bindings/javascript/package.json. Just remember to change it back before publishing.

[dikatok]

@Brooooooklyn ahhh, thank you ❤️, do you have better alternative for linking local wasm project to another project for local development without having to do that?

[dikatok]

@Brooooooklyn in the generated index.js file, is it not possible to automatically look for ./turso.wasi-browser.js as well?