Merge pull request #813 from redwoodjs/debug-windows/paths

debug windows/paths

Author: justinvdm

.github/workflows/windows-debug.yml

@@ -0,0 +1,39 @@
+name: Windows Debug Session
+
+on:
+  workflow_dispatch:
+
+jobs:
+  debug:
+    runs-on: windows-latest
+    timeout-minutes: 60
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Setup pnpm
+        uses: pnpm/action-setup@v3
+        with:
+          version: 8
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: "pnpm"
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Setup tmate session
+        shell: powershell
+        run: |
+          echo "Installing tmate..."
+          choco install tmate -y
+          echo "Starting tmate session..."
+          tmate new-session -d
+          tmate wait tmate-ready
+          $SshConnectionString = tmate display -p '#{tmate_ssh}'
+          echo "::notice title=tmate SSH session::$SshConnectionString"
+          sleep 3600

.notes/justin/worklogs/2025-10-09-windows-integration-investigation.md

@@ -0,0 +1,20 @@
+# 2025-10-09: Investigate Windows Integration Issues
+
+## Problem
+
+The SDK has several known issues when running on Windows. These seem to be primarily related to file path handling, leading to errors during development server startup and other filesystem operations. I don't have a Windows machine for testing, which makes debugging these problems difficult.
+
+Known errors include:
+- `ERR_UNSUPPORTED_ESM_URL_SCHEME`: Node.js's ESM loader receives a path with a drive letter (e.g., `c:`) instead of a `file://` URL. This indicates that absolute paths on Windows are not being correctly converted to file URLs before being passed to `import()`.
+- `ENOENT: no such file or directory`: The application attempts to create a directory at a path that appears to have a duplicated drive letter (e.g., `C:\C:\...`). This suggests an issue with path joining or normalization where an absolute path is being incorrectly concatenated with another path segment that includes the drive root.
+
+The goal is to establish a reliable method for debugging the SDK on a Windows environment to identify and fix these and any other platform-specific issues.
+
+## Plan
+
+1.  **Set up a debugging environment**: Create a GitHub Actions workflow that provides a shell on a Windows runner. This will serve as a remote debugging environment.
+2.  **Use tmate for SSH access**: The workflow will use `tmate` to create a remote SSH session, allowing interactive access to the Windows runner to run commands, inspect the filesystem, and debug the SDK in a live environment.
+3.  **Reproduce the errors**: Once the environment is accessible, the next step will be to run the playground examples or other test cases to reproduce the reported path issues.
+4.  **Investigate and fix**: With a reproducible case, I can start debugging the code to find the root cause of the path handling problems and implement fixes. This will likely involve ensuring all path manipulations are handled in a platform-agnostic way, possibly using Node's `path` module more consistently and using `pathToFileURL` from the `url` module where appropriate.
+
+This work log will track the progress of this investigation.