@usequark/quark-create-app 1.27.3 → 1.27.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@usequark/quark-create-app",
-  "version": "1.27.3",
+  "version": "1.27.4",
   "description": "CLI to scaffold new Quark projects with Next.js, Prisma, BullMQ, and Railway deployment",
   "keywords": [
     "quark",

package/templates/base-project/apps/web/src/lib/analytics/umami-config.js

@@ -67,7 +67,7 @@ export const UMAMI_PROXY_RECORD_PATH = "/s/api/record";
 
 // Server-side upstream preference: an operator that wants the analytics host
 // out of the client bundle entirely sets UMAMI_UPSTREAM_URL (or UMAMI_URL)
-// and the rewrite/handler destination follows it. NEXT_PUBLIC_UMAMI_URL
+// and the handler destination follows it. NEXT_PUBLIC_UMAMI_URL
 // remains the default so existing deployments keep working with no new vars.
 export function getUmamiUpstreamBase(env = process.env) {
 	const candidates = [

package/templates/base-project/apps/web/src/lib/analytics/umami-web-vitals.js

@@ -97,8 +97,11 @@ export function dispatchMetric(metric) {
 	const body = JSON.stringify(payload);
 
 	// First-party ingest: same-origin POSTs survive blocklists that match the
-	// upstream analytics host as third-party.
-	const endpoint = config.proxySendUrl || `${config.url}/api/send`;
+	// upstream analytics host as third-party. The client config carries no
+	// upstream URL, so there is no direct-mode fallback — when disabled the
+	// function already returned above.
+	const endpoint = config.proxySendUrl;
+	if (!endpoint) return;
 
 	// Use sendBeacon for reliability during page lifecycle transitions.
 	if (navigator.sendBeacon) {