Fix uuid randomness on wasm32 and update runner signature

- Add uuid with js feature for wasm32 in smbcloud-auth-sdk-wasm
- Change Runner::from to accept &Path instead of &PathBuf
- Bump npm sdk-auth package to 0.3.35

Author: keypair34

Cargo.lock

@@ -30,3 +30,9 @@ smbcloud-networking = { workspace = true }
 smbcloud-auth-sdk = { workspace = true }
 wasm-bindgen = { workspace = true }
 wasm-bindgen-futures = "0.4.50"
+
+# uuid's v4 feature needs a randomness source on wasm32-unknown-unknown.
+# The `js` feature wires it to the Web Crypto API (crypto.getRandomValues).
+# This only activates when building for wasm32 targets.
+[target.'cfg(target_arch = "wasm32")'.dependencies]
+uuid = { version = "1", features = ["js"] }

crates/smbcloud-auth-sdk-wasm/Cargo.toml

@@ -4,7 +4,7 @@ use {
     serde_repr::{Deserialize_repr, Serialize_repr},
     std::{
         fmt::{self, Display, Formatter},
-        path::PathBuf,
+        path::Path,
     },
 };
 
@@ -54,7 +54,7 @@ pub enum SwiftFramework {
 }
 
 impl Runner {
-    pub fn from(repo_path: &PathBuf) -> Result<Runner, ErrorResponse> {
+    pub fn from(repo_path: &Path) -> Result<Runner, ErrorResponse> {
         // Any package.json-driven app belongs on the NodeJs runner.
         // Framework-specific checks are not reliable because modern Next.js apps
         // do not need a next.config.* file at all.

crates/smbcloud-model/src/runner.rs

@@ -1,7 +1,7 @@
 {
   "name": "@smbcloud/sdk-auth",
   "description": "Browser Auth SDK for smbCloud, built from Rust and WebAssembly.",
-  "version": "0.3.34",
+  "version": "0.3.35",
   "type": "module",
   "main": "dist/smbcloud_auth_wasm.js",
   "module": "dist/smbcloud_auth_wasm.js",