Summary
The new CLI init flow for WebViewer projects (proofkit init --appType webviewer) no longer installs the FileMaker add-on to the user's machine. The old flow called installFmAddon({ addonName: "wv" }) via ensureWebViewerAddonInstalled() in packages/cli/src/installers/proofkit-webviewer.ts, which copied the ProofKitWV add-on into the FileMaker Extensions/AddonModules directory.
The new core init pipeline (planInit.ts / executeInitPlan.ts) does not call this function. The old installer code still exists but is unused by the new flow.
Expected behavior
When scaffolding a WebViewer project, the CLI should install the ProofKit WebViewer add-on to the user's local FileMaker add-on directory (as the old flow did), or at minimum prompt/instruct the user to install it.
Current behavior
The add-on installation step is skipped entirely. Users must manually install the add-on, but there's no indication that this is required.
Summary
The new CLI init flow for WebViewer projects (
proofkit init --appType webviewer) no longer installs the FileMaker add-on to the user's machine. The old flow calledinstallFmAddon({ addonName: "wv" })viaensureWebViewerAddonInstalled()inpackages/cli/src/installers/proofkit-webviewer.ts, which copied theProofKitWVadd-on into the FileMaker Extensions/AddonModules directory.The new core init pipeline (
planInit.ts/executeInitPlan.ts) does not call this function. The old installer code still exists but is unused by the new flow.Expected behavior
When scaffolding a WebViewer project, the CLI should install the ProofKit WebViewer add-on to the user's local FileMaker add-on directory (as the old flow did), or at minimum prompt/instruct the user to install it.
Current behavior
The add-on installation step is skipped entirely. Users must manually install the add-on, but there's no indication that this is required.