@xingwangzhe/stalux 1.29.7 → 1.29.8

package/README.md

@@ -172,7 +172,7 @@ bingClarityId: "YOUR_CLARITY_PROJECT_ID"
 
 > The Partytown migration in this branch is an unpublished candidate. Representative route measurements show lower TBT, but LCP regresses on the homepage and category page, so performance validation is incomplete. The following describes the candidate implementation.
 
-`stalux()` includes Partytown. The Google Analytics, Clarity, Umami, and Vercount scripts run in a Web Worker without an additional consumer integration. Page tracking follows `astro:page-load`; browsers with `Element.moveBefore()` preserve the worker during navigation. Vercount binds its counters again after the incoming page DOM is ready.
+`stalux()` includes Partytown. The Google Analytics, Clarity, and Umami scripts run in a Web Worker without an additional consumer integration. Page tracking follows `astro:page-load`; browsers with `Element.moveBefore()` preserve the worker during navigation. Vercount loads asynchronously in the main window, avoiding worker startup and DOM bridge delays for visible counters. It runs once after each `astro:page-load` to bind incoming page counters and use the current URL and first-party visitor cookie.
 
 For Google Analytics, turn off **Page changes based on browser history events** under **Admin → Data streams → Enhanced measurement → Page views → Advanced settings**. Stalux sets `send_page_view: false` and sends the URL and title for each navigation explicitly. GA's history tracking must also be disabled in the property to prevent duplicate soft-navigation pageviews. Other enhanced measurement options can remain enabled. See [Google's pageview documentation](https://developers.google.com/analytics/devguides/collection/ga4/views).
 

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@xingwangzhe/stalux",
-    "version": "1.29.7",
+    "version": "1.29.8",
     "description": "A powerful, modern Astro blog theme — use as template or install as plugin",
     "keywords": [
         "astro",

package/src/components/stalux/archives/archivesList.astro

@@ -67,7 +67,9 @@ const archiveYears = [...archivesByYearMonth.entries()]
             {archiveYear.months.map(({ month, posts: monthPosts }) => (
                 <div
                     class={styles.monthSection}
-                    style={{ "--archive-estimate": `${Math.ceil(monthPosts.length / 12) * 12 * 48 + 40}px` }}
+                    style={{
+                        "--archive-estimate": `${Math.ceil(monthPosts.length / 12) * 12 * 48 + 40}px`,
+                    }}
                 >
                     <h3 class={styles.monthTitle}>{t("archives.month", { n: month })}</h3>
                     {Array.from({ length: Math.ceil(monthPosts.length / 12) }, (_, index) =>

package/src/scripts/analytics-runtime.ts

@@ -1,5 +1,5 @@
 /**
- * Keep third-party code in Partytown. This small main-thread bridge owns the
+ * Keep analytics trackers in Partytown. This small main-thread bridge owns the
  * Astro navigation lifecycle and tells the worker about each completed page.
  */
 declare global {
@@ -116,12 +116,15 @@ function trackUmamiPage(): void {
 }
 
 function trackVercountPage(): void {
-    // Vercount captures its display elements at startup. A new Astro body needs
-    // a new worker execution so the counters refer to the incoming DOM.
+    // Visible counters need the current window's URL, cookie and DOM nodes.
+    // Avoid worker startup and synchronous DOM bridges; bind fresh nodes once
+    // per completed Astro navigation using the small upstream async script.
     document.querySelector("script[data-stalux-vercount]")?.remove();
-    appendWorkerScript("https://events.vercount.one/js", {
-        "data-stalux-vercount": "true",
-    });
+    const script = document.createElement("script");
+    script.async = true;
+    script.src = "https://events.vercount.one/js";
+    script.dataset.staluxVercount = "true";
+    document.head.appendChild(script);
 }
 
 if (!state.installed) {