@synopackageland/cli 0.33.1 → 0.33.2

package/CHANGELOG.md

@@ -1,9 +1,6 @@
 # Changelog
 
-## 0.33.1 (2026-10-27)
+## 0.33.2 (2026-10-28)
 
-- Use one NAS connection path for host login, secure session storage, TLS and every DSM request, including package commands, deployment, ctl transfers and e2e login helpers
-- Accept self-signed, untrusted CA, hostname-mismatched and expired NAS certificates by default
-- Record each leaf SHA-256 for display; warn once and update it when a certificate changes, then continue
-- Add opt-in --strict-tls for host profiles and individual commands; --ca also verifies CA trust, hostname, validity and recorded certificates
-- Keep passwords on the exact connection whose certificate was inspected, without changing global TLS settings
+- Load the installed app when a DSM window opens after a package upgrade without a page reload; the loader previously reused the app module the previous build left in the page
+- Give DSM windows and full pages `ctx.uiUpdate.check()`, which reports when the installed package has replaced the UI the page loaded, so the SDK's AppShell can offer a reload after an upgrade

package/README.md

@@ -282,8 +282,10 @@ for every other frontend. Plain/binary scaffolds explicitly choose new-page; Vue
 native `ui.launch` resolves to `dsm-window`; the CLI does not guess a frontend's
 framework from its build command. `new-page` registers DSM `type: "standalone"`,
 so the main menu and Package Center open a full page on the DSM origin.
-`ctx.fullPage`, `ctx.appIcon`, session/SynoToken, launch parameters and entry
-permissions use the same wrapper in both modes. The wrapper sets the standalone
+`ctx.fullPage`, `ctx.appIcon`, `ctx.uiUpdate`, session/SynoToken, launch parameters and entry
+permissions use the same wrapper in both modes. `ctx.uiUpdate.check()` reports when
+a package upgrade replaced the UI the page loaded; SDK 0.31.5+ AppShell then shows
+a one-line reload notice. The wrapper sets the standalone
 page title, favicon and device-width viewport. It retains ExtJS; `pureEnv` is
 not appropriate, and alternate Portal ports are not needed (`allowAltPort` is omitted).
 

package/dist/standalone/dsm-window.d.ts

@@ -49,6 +49,8 @@ export declare function renderUiConfig(manifest: StandaloneManifest, icons?: Pac
  * (and add a device-width viewport), and `ctx.appIcon` is the package icon a
  * full-page shell shows beside the name, where a DSM window has a title bar.
  * A portal App's `ctx.portal` shows `portalText`, the SDK's panel text.
+ * `ctx.uiUpdate.check()` answers whether the installed package replaced this
+ * window's UI (the SDK's AppShell then offers a reload).
  * `ctx.launchParams` holds the App's own values from the launch that opened
  * the window (a `launchParam` desktop URL or `SYNO.SDS.AppLaunch(id, param)`),
  * and `ctx.onLaunch(fn)` hands fn those of each later launch with values.

package/dist/standalone/dsm-window.js

@@ -213,6 +213,8 @@ export function renderUiConfig(manifest, icons = packageIcons(manifest.icon), lo
  * (and add a device-width viewport), and `ctx.appIcon` is the package icon a
  * full-page shell shows beside the name, where a DSM window has a title bar.
  * A portal App's `ctx.portal` shows `portalText`, the SDK's panel text.
+ * `ctx.uiUpdate.check()` answers whether the installed package replaced this
+ * window's UI (the SDK's AppShell then offers a reload).
  * `ctx.launchParams` holds the App's own values from the launch that opened
  * the window (a `launchParam` desktop URL or `SYNO.SDS.AppLaunch(id, param)`),
  * and `ctx.onLaunch(fn)` hands fn those of each later launch with values.
@@ -394,9 +396,14 @@ ${ns}.sessionUser = function () {
   return { name: typeof session.user === "string" ? session.user : "", isAdmin: session.is_admin === true };
 };
 
-${root ? root.definitions : ""}${manifest.portal ? renderPortalDefinition(ns, portalText) : ""}${ns}.loadApp = function (done) {
+${root ? root.definitions : ""}${manifest.portal ? renderPortalDefinition(ns, portalText) : ""}// DSM loads the installed build's window script when a window opens after a
+// package upgrade, but keeps the page and the app module the previous build
+// registered. Reuse it only when this build loaded it; an older loader records
+// no build, so its app is replaced as well.
+${ns}.loadApp = function (done) {
   var apps = window.DsmPackageApps || {};
-  if (apps[${p}]) {
+  var versions = window.DsmPackageAppVersions = window.DsmPackageAppVersions || {};
+  if (apps[${p}] && versions[${p}] === "${assetVersion}") {
     done(apps[${p}]);
     return;
   }
@@ -408,10 +415,29 @@ ${root ? root.definitions : ""}${manifest.portal ? renderPortalDefinition(ns, po
   var js = document.createElement("script");
   js.src = base + "app.js?v=${assetVersion}";
   js.dataset.package = ${p};
-  js.onload = function () { done((window.DsmPackageApps || {})[${p}]); };
+  js.onload = function () { versions[${p}] = "${assetVersion}"; done((window.DsmPackageApps || {})[${p}]); };
   document.head.appendChild(js);
 };
 
+// DSM keeps a loaded window script after a package upgrade until the page
+// reloads, so a window opened again runs the old UI. ui/config names the
+// installed build's window file: once it no longer names this one, the
+// installed UI replaced this page's. no-store, not no-cache: DSM tags
+// ui/config by size alone, so a revalidation can keep an older build's copy.
+// An uninstalled package or a failed read answers false.
+${ns}.uiUpdate = {
+  check: function (signal) {
+    if (typeof fetch !== "function") return Promise.resolve(false);
+    return fetch("webman/3rdparty/${pkg}/config", { cache: "no-store", credentials: "same-origin", signal: signal })
+      .then(function (response) { return response.ok ? response.json() : null; })
+      .then(function (config) {
+        return !!config && typeof config === "object" && !Array.isArray(config) &&
+          !Object.prototype.hasOwnProperty.call(config, ${JSON.stringify(windowScriptName(manifest))});
+      })
+      .catch(function () { return false; });
+  }
+};
+
 // A Portal/standalone launch is the whole page, on a phone as well: no desktop
 // minimum width, and the app lays itself out full-page.
 ${ns}.fullPage = function () {
@@ -501,6 +527,7 @@ ${root ? root.mount : ""}    ${ns}.loadApp(function (app) {
           appWindow: me,
           fullPage: ${ns}.fullPage(),
           appIcon: ${ns}.appIcon,
+          uiUpdate: ${ns}.uiUpdate,
           lang: lang,
           locale: i18n.locale,
           t: i18n.t${root ? `,\n          executor: access` : ""}

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@synopackageland/cli",
-  "version": "0.33.1",
+  "version": "0.33.2",
   "description": "Syno Package Land Developer Kit CLI",
   "type": "module",
   "bin": {
-    "synopkgland": "dist/bin.js"
+    "synopkgland": "./dist/bin.js"
   },
   "engines": {
     "node": ">=22.12"

package/skills/SKILL.md

@@ -184,7 +184,7 @@ Scaffold 明確寫入此選擇，plain／binary 使用 `new-page`，Vue UI SDK
 預設的 `dsm-window`（省略 `ui.launch`）。原生 manifest 省略 `ui.launch` 時解析為 `dsm-window`，CLI 不猜測前端依賴。
 
 `new-page` 產生 DSM `type: "standalone"` launcher，主選單及套件中心皆在 DSM
-本身的 origin 開啟全頁。`ctx.fullPage`、`ctx.appIcon`、SynoToken／session、
+本身的 origin 開啟全頁。`ctx.fullPage`、`ctx.appIcon`、`ctx.uiUpdate`、SynoToken／session、
 `ctx.launchParams`／`onLaunch`、`entry` 權限沿用共用 wrapper；全頁的標題、
 favicon 與手機 viewport 由 wrapper 設定。不需要 `pureEnv` 或 `allowAltPort`。
 

package/skills/reference/create.md

@@ -231,7 +231,7 @@ Scaffold 明確寫入此選擇，plain／binary 使用 `new-page`，Vue UI SDK
 預設的 `dsm-window`（省略 `ui.launch`）。原生 manifest 省略 `ui.launch` 時解析為 `dsm-window`，CLI 不猜測前端依賴。
 
 `new-page` 產生 DSM `type: "standalone"` launcher，主選單及套件中心皆在 DSM
-本身的 origin 開啟全頁。`ctx.fullPage`、`ctx.appIcon`、SynoToken／session、
+本身的 origin 開啟全頁。`ctx.fullPage`、`ctx.appIcon`、`ctx.uiUpdate`、SynoToken／session、
 `ctx.launchParams`／`onLaunch`、`entry` 權限沿用共用 wrapper；全頁的標題、
 favicon 與手機 viewport 由 wrapper 設定。不需要 `pureEnv` 或 `allowAltPort`。
 

package/skills/reference/portal.md

@@ -49,7 +49,7 @@ Scaffold 明確寫入此選擇，plain／binary 使用 `new-page`，Vue UI SDK
 預設的 `dsm-window`（省略 `ui.launch`）。原生 manifest 省略 `ui.launch` 時解析為 `dsm-window`，CLI 不猜測前端依賴。
 
 `new-page` 產生 DSM `type: "standalone"` launcher，主選單及套件中心皆在 DSM
-本身的 origin 開啟全頁。`ctx.fullPage`、`ctx.appIcon`、SynoToken／session、
+本身的 origin 開啟全頁。`ctx.fullPage`、`ctx.appIcon`、`ctx.uiUpdate`、SynoToken／session、
 `ctx.launchParams`／`onLaunch`、`entry` 權限沿用共用 wrapper；全頁的標題、
 favicon 與手機 viewport 由 wrapper 設定。不需要 `pureEnv` 或 `allowAltPort`。
 

package/skills/reference/ui-vue.md

@@ -173,7 +173,7 @@ Scaffold 明確寫入此選擇，plain／binary 使用 `new-page`，Vue UI SDK
 預設的 `dsm-window`（省略 `ui.launch`）。原生 manifest 省略 `ui.launch` 時解析為 `dsm-window`，CLI 不猜測前端依賴。
 
 `new-page` 產生 DSM `type: "standalone"` launcher，主選單及套件中心皆在 DSM
-本身的 origin 開啟全頁。`ctx.fullPage`、`ctx.appIcon`、SynoToken／session、
+本身的 origin 開啟全頁。`ctx.fullPage`、`ctx.appIcon`、`ctx.uiUpdate`、SynoToken／session、
 `ctx.launchParams`／`onLaunch`、`entry` 權限沿用共用 wrapper；全頁的標題、
 favicon 與手機 viewport 由 wrapper 設定。不需要 `pureEnv` 或 `allowAltPort`。