pi-revit 0.1.6 → 0.1.7

package/README.md

@@ -70,10 +70,10 @@ pi install npm:pi-revit
 cd "$env:USERPROFILE\.pi\agent\npm\node_modules\pi-revit"
 
 # 3. Build + deploy the Revit add-in (RevitBridge.dll + the Roslyn DLLs for execute_csharp).
-npm run deploy
+npm.cmd run deploy
 
 # 4. Create the workspace and global pi-revit command.
-npm run setup
+npm.cmd run setup
 ```
 
 For a non-default Revit install location, use the PowerShell deploy script directly and pass
@@ -111,7 +111,7 @@ That's all. Pi starts with the Revit tools ready:
 > select all structural columns
 ```
 
-**How this works:** install step 3 placed a small `pi-revit` command in the same folder as the
+**How this works:** the setup step placed a small `pi-revit` command in the same folder as the
 `pi` command itself. That folder is on your system PATH — which is exactly why *every* terminal
 finds `pi-revit`, with no extra configuration. When you run it, it switches to your workspace at
 `Documents\pi-revit` and starts Pi there, so your conventions file (`AGENTS.md`) loads
@@ -165,12 +165,11 @@ Plain `pi` from any folder also works; `pi-revit` just adds the right working fo
 
 ### npm install
 
-Close Revit, then in PowerShell:
+Close Revit, then in PowerShell — from any folder **outside** the installed package (Windows
+cannot delete a folder your shell is standing in):
 
 ```powershell
-cd "$env:USERPROFILE\.pi\agent\npm\node_modules\pi-revit"
-powershell -ExecutionPolicy Bypass -File scripts\uninstall.ps1
-pi remove npm:pi-revit
+powershell -ExecutionPolicy Bypass -File "$env:USERPROFILE\.pi\agent\npm\node_modules\pi-revit\scripts\uninstall.ps1"
 ```
 
 ### Source install
@@ -182,9 +181,9 @@ powershell -ExecutionPolicy Bypass -File scripts\uninstall.ps1
 ```
 
 This removes the Revit bridge add-in (every installed Revit version), the global `pi-revit`
-command, and the bridge runtime folder (`%APPDATA%\RevitBridge\`). It also removes the Pi
-package registration for source installs; npm installs should additionally run
-`pi remove npm:pi-revit` as shown above. Your workspace at `Documents\pi-revit` (notes + session
+command, the bridge runtime folder (`%APPDATA%\RevitBridge\`), and the Pi package registration
+(it tries both the npm and the source-install form, so no extra `pi remove` is needed for
+either install kind). Your workspace at `Documents\pi-revit` (notes + session
 history) is **preserved** — add `-RemoveWorkspace` to delete it too, or `-RevitVersion 2026` to
 target a single Revit version. Pi itself is left installed; remove it with
 `npm uninstall -g @earendil-works/pi-coding-agent` if you want.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-revit",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "description": "Native Pi connector for Autodesk Revit. Run npx.cmd -y pi-revit for the full Windows install.",
   "author": "Ahmad Altahlawi",
   "license": "MIT",

package/scripts/uninstall.ps1

@@ -96,14 +96,30 @@ Remove-IfExists (Join-Path $env:APPDATA 'RevitBridge') 'bridge runtime folder'
 #    is actually registered, so a machine with both gets both removed.
 if ($pi) {
     $repoRoot = Split-Path $PSScriptRoot -Parent
-    Push-Location $repoRoot
+    # When this script runs from the npm-installed copy, `pi remove npm:pi-revit`
+    # deletes the very folder the script lives in — and Windows fails that delete
+    # (EBUSY) while any working directory sits inside it. Step our own process out
+    # if needed; the calling shell's location we can only warn about.
+    if ($repoRoot -match '\\node_modules\\' -and
+        (Get-Location).Path.StartsWith($repoRoot, [StringComparison]::OrdinalIgnoreCase)) {
+        Set-Location $env:SystemRoot
+        Write-Warning "This PowerShell was started inside $repoRoot. If the package removal below fails, run 'cd \' in your shell and re-run the uninstall."
+    }
     try {
         $removed = @()
-        foreach ($source in @('npm:pi-revit', './')) {
-            $global:LASTEXITCODE = 0
-            & pi remove $source
-            if ($LASTEXITCODE -eq 0) {
-                $removed += $source
+        # './' resolves against the repo root, so it runs from there — and first,
+        # while this folder is guaranteed to still exist. 'npm:pi-revit' then runs
+        # from a neutral directory so no working directory blocks the folder delete.
+        foreach ($source in @('./', 'npm:pi-revit')) {
+            Push-Location $(if ($source -eq './') { $repoRoot } else { $env:SystemRoot })
+            try {
+                $global:LASTEXITCODE = 0
+                & pi remove $source
+                if ($LASTEXITCODE -eq 0) {
+                    $removed += $source
+                }
+            } finally {
+                Pop-Location
             }
         }
         if ($removed.Count -gt 0) {
@@ -113,8 +129,6 @@ if ($pi) {
         }
     } catch {
         Write-Warning "Could not auto-remove the Pi package; run 'pi remove npm:pi-revit' (npm install) or 'pi remove ./' from this repo (install from source). ($_)"
-    } finally {
-        Pop-Location
     }
 }