komado 0.1.2 → 0.1.3

package/README.md

@@ -52,19 +52,28 @@ Then just type **`komado`**. Re-run that same command any time to update. It nee
 `git`, **Node ≥ 20**, and `npm`; it installs to `~/.local/share/komado` with the
 launcher in `~/.local/bin` (override via `KOMADO_APP_DIR` / `KOMADO_BIN_DIR`).
 
-**Windows** — the PowerShell one-liner installs Node.js for you (via `winget`) if it's
-missing, then komado, leaving a native `komado` command on your `PATH`:
+**Windows** — one line installs Node.js for you (via `winget`) if it's missing,
+then komado, leaving a native `komado` command on your `PATH`. Works from **both
+CMD and PowerShell**, and ignores the execution policy either way:
 
-```powershell
-irm https://raw.githubusercontent.com/RyuPrad/komado/main/install.ps1 | iex
+```
+powershell -NoProfile -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/RyuPrad/komado/main/install.ps1 | iex"
 ```
 
-Already have **Node ≥ 20**? Install straight from PowerShell or CMD instead:
+Prefer the native syntax? In **PowerShell**:
 
 ```powershell
-npm i -g komado
+irm https://raw.githubusercontent.com/RyuPrad/komado/main/install.ps1 | iex
 ```
 
+Already have **Node ≥ 20**? `npm i -g komado` works from either shell — CMD runs
+npm's `.cmd` shim directly, and PowerShell does too if your execution policy
+allows scripts.
+
+> Note: the short `irm … | iex` form is PowerShell-only — in **CMD** it prints
+> `'irm' is not recognized`. Use the longer one-liner above (which works in both),
+> or run `npm i -g komado` directly.
+
 Don't use the `curl … | bash` line on Windows — under **Git Bash** or **WSL** it
 installs a launcher that only runs inside that shell, never from CMD/PowerShell.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "komado",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "A terminal manga reader (MangaDex + local files) rendered with Ink.",
   "keywords": [
     "manga",