clone and update both end in bun install

a checkout with no node_modules does not run, so cloning without installing left
something that looked finished and was not.

run after an update too, and UNCONDITIONALLY — including when the pull changed
nothing. skipping it on "already up to date" is the shortcut that is right until
the one time it is not, and an install on an unchanged tree is close to free.

`process.execPath`, NEVER the string "bun". verified on fofos today: PM2 started
officer with PATH=/usr/local/sbin:…:/snap/bin and bun lives in ~/.bun/bin, so
looking it up by name fails inside the process and works perfectly when you run the
same command by hand — the worst version of this bug, because it cannot be
reproduced the obvious way. execPath is the bun already running us.

bun's directory is also prepended to PATH for the child, which execPath alone does
not cover: a postinstall script calling `bun` would not find it, and that reads as
a broken package rather than a missing PATH entry.

the two commands report as ONE, each prefixed with the line that produced it, so
the panel reads like the terminal somebody would otherwise have opened. it stops at
the first failure — installing into a clone that did not happen produces a second,
more confusing error about a directory that is not there — and a clone that worked
followed by an install that did not is legible as exactly that.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

pastilhas

2026-08-29 00:54:58 +01:00

co-authored by

Claude Opus 5

parent df394e29a4

commit bab47526f7

2 changed files with 57 additions and 4 deletions

									
										manifest.ts
									
		+1
		-1
	
												View File
												
				@@ -35,7 +35,7 @@ import type { PluginManifest } from '@@/plugins/manifest';

				 */

				export const manifest: PluginManifest = {

				  publisher: 'officerdev',

				  version: '2026.08.29.10',

				  version: '2026.08.29.11',

				  platform: '>=1.0.0',

				  label: 'Fofos',