@rubytech/create-maxy 1.0.785 → 1.0.787

package/dist/index.js

@@ -1358,6 +1358,19 @@ function buildPlatform() {
     // server/package.json but NOT shipped as pre-built node_modules — npm pack silently
     // strips files from nested node_modules (e.g. rxjs/package.json), breaking require().
     // Install fresh on device to guarantee a complete dependency tree.
+    //
+    // On upgrade, wipe `node_modules` first so npm extracts a clean tree. Without
+    // this, an interrupted previous install (network blip, operator cancellation,
+    // power loss) can leave nested package.json files half-truncated — the most
+    // common manifestation is `Error: Invalid package config .../rxjs/package.json`
+    // at server startup, which loops the brand service indefinitely. The wipe
+    // adds ~30 s to upgrades but eliminates a class of unrecoverable customer
+    // states; reliability wins over speed for a one-shot install path.
+    const serverNodeModules = join(INSTALL_DIR, "server", "node_modules");
+    if (existsSync(serverNodeModules)) {
+        console.log("  Wiping previous server/node_modules for a clean reinstall...");
+        rmSync(serverNodeModules, { recursive: true, force: true });
+    }
     console.log(`  Installing server dependencies (${join(INSTALL_DIR, "server")})...`);
     shellRetry("npm", ["install", "--omit=dev", ...NPM_NET_FLAGS], { cwd: join(INSTALL_DIR, "server") }, 3, 15);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy",
-  "version": "1.0.785",
+  "version": "1.0.787",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy": "./dist/index.js"

package/payload/platform/scripts/wifi-provision-server/server.js

@@ -292,12 +292,10 @@ function portalHTML() {
       <div class="success-icon">&#10003;</div>
       <h1>Connected!</h1>
       <p class="hint">${escapedBrandName} is now online. Redirecting in <span id="redirect-countdown">15</span>s…</p>
-      <div class="address-box">
-        <a id="device-link" href="#"></a>
-      </div>
-      <p class="hint" id="manual-hint" style="display:none">If your phone doesn't redirect automatically, open this in your normal browser:</p>
-      <div class="address-box" id="manual-box" style="display:none">
-        <span id="device-link-text" style="user-select:all"></span>
+      <a id="open-btn" href="#" class="btn" style="text-decoration:none;display:flex;align-items:center;justify-content:center">Open ${escapedBrandName} →</a>
+      <p class="hint" style="margin-top:16px">Or copy this URL into your browser:</p>
+      <div class="address-box" style="user-select:all" id="manual-box">
+        <span id="device-link-text"></span>
       </div>
       <p class="hint">This access point will close shortly.<br>Your phone will reconnect to your WiFi automatically.</p>
     </div>
@@ -421,21 +419,11 @@ function portalHTML() {
     var ipAddr = data.ip ? "http://" + data.ip + devicePort : null;
     // Auto-navigate target: prefer the IP because mDNS .local resolution
     // is flaky on Android (notably Brave) and the redirect dead-ends.
-    // The displayed link uses the same URL so what the user sees is what
-    // they get if they tap.
     var redirectAddr = ipAddr || hostnameAddr;
-    var link = document.getElementById("device-link");
-    link.href = redirectAddr;
-    link.textContent = redirectAddr;
-    // Always surface a manual fallback line — captive webviews on some
-    // phone OSes silently swallow JS navigation, and the user needs to
-    // be able to copy-paste the URL into a real browser.
+    var openBtn = document.getElementById("open-btn");
+    if (openBtn) openBtn.href = redirectAddr;
     var manualText = document.getElementById("device-link-text");
-    if (manualText) {
-      manualText.textContent = redirectAddr;
-      document.getElementById("manual-hint").style.display = "block";
-      document.getElementById("manual-box").style.display = "block";
-    }
+    if (manualText) manualText.textContent = redirectAddr;
     showScreen("success-screen");
     // 15s countdown: the Pi keeps the AP up for ~10s after writing the
     // success result so this poll can land, then tears it down; the
@@ -667,8 +655,22 @@ function handleRequest(req, res) {
         // Use async open+write to avoid blocking the event loop (a FIFO
         // write blocks until a reader opens the other end).
         connecting = true;
-        res.writeHead(202, { "Content-Type": "application/json" });
-        res.end('{"status":"connecting"}');
+        // Return success immediately with the post-connect URL info.
+        // Why not poll for verification? The AP and station modes are
+        // mutually exclusive on a single radio: as soon as the bash
+        // script tears down hostapd to run `nmcli connect`, the phone
+        // loses its connection to 192.168.4.1 and any subsequent
+        // `/result` poll dies. The success page must be in the phone's
+        // hands BEFORE the AP goes away. We send the hostname (.local
+        // resolution works on iOS/macOS) and the operator can paste
+        // the URL into a browser if .local fails on their device.
+        res.writeHead(200, { "Content-Type": "application/json" });
+        res.end(JSON.stringify({
+          success: true,
+          hostname: HOSTNAME,
+          // ip is intentionally absent: we don't yet know the new
+          // home-WiFi IP and the AP IP (192.168.4.1) is about to die.
+        }));
 
         const fifoData = `${ssid}\n${password}`;
         fs.open(CONNECT_FIFO, "w", (err, fd) => {