gsd-lite 0.7.7 → 0.7.8
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/.claude-plugin/marketplace.json +1 -1
- package/.claude-plugin/plugin.json +1 -1
- package/install.js +19 -2
- package/package.json +1 -1
|
@@ -13,7 +13,7 @@
|
|
|
13
13
|
"name": "gsd",
|
|
14
14
|
"source": "./",
|
|
15
15
|
"description": "AI orchestration tool — GSD management shell + Superpowers quality core. 5 commands, 4 agents, 5 workflows, MCP server, context monitoring.",
|
|
16
|
-
"version": "0.7.
|
|
16
|
+
"version": "0.7.8",
|
|
17
17
|
"keywords": [
|
|
18
18
|
"orchestration",
|
|
19
19
|
"mcp",
|
package/install.js
CHANGED
|
@@ -210,7 +210,19 @@ export function main() {
|
|
|
210
210
|
|
|
211
211
|
// 6. Stable runtime for MCP server
|
|
212
212
|
copyDir(join(__dirname, 'src'), join(RUNTIME_DIR, 'src'), 'runtime/src → ~/.claude/gsd/src/');
|
|
213
|
-
|
|
213
|
+
// Write a sanitized package.json: strip dev-only npm lifecycle scripts
|
|
214
|
+
// (prepare/prepublishOnly/version use POSIX shell + dev tooling absent from
|
|
215
|
+
// the runtime). Leaving them in means a later manual `npm install` in
|
|
216
|
+
// ~/.claude/gsd fails under cmd.exe on Windows (issue #2).
|
|
217
|
+
if (DRY_RUN) {
|
|
218
|
+
log(' [dry-run] Would write runtime/package.json (dev scripts stripped)');
|
|
219
|
+
} else {
|
|
220
|
+
const runtimePkg = JSON.parse(readFileSync(join(__dirname, 'package.json'), 'utf-8'));
|
|
221
|
+
delete runtimePkg.scripts;
|
|
222
|
+
mkdirSync(RUNTIME_DIR, { recursive: true });
|
|
223
|
+
writeFileSync(join(RUNTIME_DIR, 'package.json'), JSON.stringify(runtimePkg, null, 2) + '\n');
|
|
224
|
+
log(' ✓ runtime/package.json → ~/.claude/gsd/package.json (scripts stripped)');
|
|
225
|
+
}
|
|
214
226
|
// Copy uninstall.js so the SessionStart hook's Phase 0 orphan-cleanup can
|
|
215
227
|
// spawn it when /plugin uninstall has removed the plugin without running our
|
|
216
228
|
// uninstaller. Without this, hooks/runtime/settings.json entries written by
|
|
@@ -230,7 +242,12 @@ export function main() {
|
|
|
230
242
|
log(' ⧗ Installing runtime dependencies...');
|
|
231
243
|
const lockFile = join(RUNTIME_DIR, 'package-lock.json');
|
|
232
244
|
const hasLockFile = existsSync(lockFile);
|
|
233
|
-
|
|
245
|
+
// --ignore-scripts: the runtime install only needs node_modules. Skipping
|
|
246
|
+
// lifecycle scripts avoids running the dev-only POSIX `prepare` git-hook
|
|
247
|
+
// setup, which fails under cmd.exe on Windows (issue #2).
|
|
248
|
+
const installCmd = hasLockFile
|
|
249
|
+
? 'npm ci --omit=dev --ignore-scripts'
|
|
250
|
+
: 'npm install --omit=dev --no-fund --no-audit --ignore-scripts';
|
|
234
251
|
try {
|
|
235
252
|
execSync(installCmd, { cwd: RUNTIME_DIR, stdio: 'pipe' });
|
|
236
253
|
log(' ✓ runtime dependencies installed');
|