@bobfrankston/rmfmail 1.2.279 → 1.2.280

package/.commitmsg

@@ -1,16 +1,19 @@
-build-tinymce: report which TinyMCE and language-pack versions were copied
+About: show the bundled editor version
 
-Both specs are caret ranges, so the resolved version moves on its own whenever
-npm re-resolves the tree — tinymce sat at 8.6.0 for weeks under a ^8.5.0 spec
-with nothing to notice ("do you track updates for TinyMCE?", Bob 2026-08-23).
+CORRECTION to 1.2.279. That release added the resolved tinymce / tinymce-i18n
+versions to build-tinymce.js's console output, on the claim that this put the
+answer in the build transcript every publish archives. It does not:
+npmglobalize swallows a sub-build's stdout and reports only "✓ Build
+succeeded", so the line never reaches c:\temp\rebuild\. The echo is still
+correct when the script is run directly, but the build log is not where this
+question gets answered.
 
-Pinning exact would only trade silent drift for silent staleness: no more patch
-fixes, and the surprise moves to whoever edits the pin. A dependency bot is the
-wrong shape too — those work by filing PRs, and this repo publishes from the
-local tree with direct commits.
+About… now carries an "Editor bundle" row — "TinyMCE 8.8.2 · 61 languages" —
+read at display time from client/lib/tinymce/package.json and langs/index.json,
+the same tree the editor loads from, so it cannot drift from what is actually
+running. That answers it on the machine showing the symptom, which is where it
+matters, rather than requiring a checkout of the matching tag.
 
-So make it visible where it already costs nothing. Every publish archives its
-build transcript to c:\temp\rebuild\, and build-tinymce.js already prints what
-it copied; it now prints the resolved versions of tinymce and tinymce-i18n as
-well. "Which TinyMCE shipped in 1.2.277?" is answerable from the log, with no
-network call at build time and nothing to maintain.
+Why this keeps mattering: both specs are caret ranges, so the resolved version
+moves whenever npm re-resolves the tree — tinymce sat at 8.6.0 for weeks under
+a ^8.5.0 spec with nothing to notice.

package/client/app.bundle.js

@@ -13315,9 +13315,27 @@ async function openAboutDialog() {
     if (e.target === backdrop) close();
   });
   try {
-    const [v, accounts] = await Promise.all([
+    const editorBundle = async () => {
+      const readJson = async (url) => {
+        try {
+          const r = await fetch(url);
+          return r.ok ? await r.json() : null;
+        } catch {
+          return null;
+        }
+      };
+      const [pkg, langs] = await Promise.all([
+        readJson("lib/tinymce/package.json"),
+        readJson("lib/tinymce/langs/index.json")
+      ]);
+      if (!pkg?.version) return "";
+      const n = langs?.length || 0;
+      return n ? `TinyMCE ${pkg.version} \xB7 ${n} languages` : `TinyMCE ${pkg.version}`;
+    };
+    const [v, accounts, editorInfo] = await Promise.all([
       getVersion().catch(() => ({})),
-      getAccounts().catch(() => [])
+      getAccounts().catch(() => []),
+      editorBundle()
     ]);
     const storage = v.storage || {};
     const isApp2 = typeof mailxapi !== "undefined" && mailxapi?.isApp;
@@ -13336,6 +13354,7 @@ async function openAboutDialog() {
     if (storage.folderId) rows.push(["Drive folderId", storage.folderId]);
     if (storage.folderOwner) rows.push(["Drive owner", storage.folderOwner]);
     if (storage.configDir) rows.push(["Config dir", storage.configDir]);
+    if (editorInfo) rows.push(["Editor bundle", editorInfo]);
     rows.push(["Accounts", String((accounts || []).length)]);
     rows.push(["User agent", navigator.userAgent]);
     rows.push(["Screen", `${screen.width}\xD7${screen.height}`]);