@raftlabs/raftstack 1.2.0 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -77,6 +77,29 @@ The wizard will:
77
77
  | `CONTRIBUTING.md` | Developer contribution guide |
78
78
  | `.github/QUICK_REFERENCE.md` | One-page workflow cheat sheet for developers |
79
79
 
80
+ ## Package Manager Support
81
+
82
+ RaftStack automatically detects and adapts to your package manager of choice:
83
+
84
+ | Package Manager | Detection Method | Lockfile |
85
+ |----------------|------------------|----------|
86
+ | **npm** | `package-lock.json` | `package-lock.json` |
87
+ | **pnpm** | `pnpm-lock.yaml` | `pnpm-lock.yaml` |
88
+ | **Yarn Classic (1.x)** | `yarn.lock` | `yarn.lock` |
89
+ | **Yarn Berry (2+)** | `yarn.lock` + `packageManager` field | `yarn.lock` |
90
+
91
+ **Auto-Detection:**
92
+ - RaftStack scans for lockfiles in your project root
93
+ - Priority order: pnpm > Yarn > npm
94
+ - For Yarn, the version is determined from the `packageManager` field in `package.json`
95
+ - If no lockfile is found, you'll be prompted to select your preferred package manager
96
+
97
+ **What Gets Customized:**
98
+ - All generated hooks use the correct package manager commands (`npx` vs `pnpm dlx` vs `yarn dlx`)
99
+ - GitHub workflows use appropriate install commands (`npm ci` vs `pnpm install --frozen-lockfile` vs `yarn install --immutable`)
100
+ - pnpm projects automatically include the `pnpm/action-setup` action in CI workflows
101
+ - Documentation shows the right commands for your package manager
102
+
80
103
  ## Commands
81
104
 
82
105
  ### `raftstack init`