Zac Gaetano
8aece9cbc4
End-to-end verification on a fresh Windows machine surfaced three issues: 1. pwsh isn't installed by default — Windows ships powershell.exe (5.1). Switched all script invocations + docs from `pwsh` to `powershell`. 2. .NET's strict XML parser rejects manifest.xml because the <Resources> comment legally contains `--` (inside `--enable-nodejs`/`--mixed-context` CEF flag names). Switched build-installer.ps1 to regex extraction, matching what build-zxp.mjs already does. 3. winget installs Inno Setup 6 to %LOCALAPPDATA%\Programs by default, not Program Files (x86). Added the user-scope path to the ISCC.exe fallback list. Verified: `powershell -File build-all.ps1` produces both artifacts — dragonflight-premiere-panel-1.0.0.zxp (35 KB, signature valid) dragonflight-premiere-panel-1.0.0-windows-setup.exe (2 MB). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
18 lines
575 B
JSON
18 lines
575 B
JSON
{
|
|
"name": "dragonflight-premiere-panel-build",
|
|
"version": "0.0.0",
|
|
"private": true,
|
|
"description": "Build pipeline for the Dragonflight Premiere Pro CEP panel — produces a signed .zxp and a Windows .exe installer.",
|
|
"type": "module",
|
|
"scripts": {
|
|
"build:zxp": "node build-zxp.mjs",
|
|
"build:exe": "powershell -NoProfile -ExecutionPolicy Bypass -File build-installer.ps1",
|
|
"build": "powershell -NoProfile -ExecutionPolicy Bypass -File build-all.ps1"
|
|
},
|
|
"devDependencies": {
|
|
"zxp-sign-cmd": "^2.0.0"
|
|
},
|
|
"engines": {
|
|
"node": ">=18"
|
|
}
|
|
}
|