waypoint-expo-template 2.0.0 → 2.1.0

package/README.md

@@ -10,8 +10,22 @@ Waypoint device-preview tile.
 src/app/_layout.tsx    plain Stack, headers off
 src/app/index.tsx      the entry screen — `/` by expo-router convention
 src/navigation.ts      which control leads where (links only)
+
+platform/              platform-owned — do not edit
+app.config.js          two lines; delegates to platform/
 ```
 
+`platform/` holds the files the platform maintains, not you. Today that is the
+base URL: the preview is embedded in the control plane under
+`/api/v1/preview/<appId>/`, and expo-router matches routes against the
+browser's pathname, so it has to be told that prefix or every screen renders
+"Unmatched Route". It comes from `EXPO_BASE_URL`, set when the platform starts
+Metro — unset (running the app yourself) the base is empty and it serves at the
+root, as normal.
+
+`app.config.js` has to sit at the root because Expo resolves its dynamic config
+from `<projectRoot>/app.config` and nowhere else. It contains no logic.
+
 ## What is deliberately NOT here
 
 No preview manifests, no compile step, no canvas protocol module, and no

package/app.config.js

@@ -0,0 +1,10 @@
+// Expo resolves its dynamic config from `<projectRoot>/app.config` and nowhere
+// else — @expo/config's getDynamicConfigFilePath does
+// `resolveFrom(projectRoot, './app.config')`. So this file cannot live in
+// platform/; it stays here as the entry point Expo requires, and holds no
+// logic of its own.
+//
+// Everything the platform maintains is in platform/. Do not edit either.
+const { withPlatformBaseUrl } = require('./platform/base-url');
+
+module.exports = ({ config }) => withPlatformBaseUrl(config);

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "waypoint-expo-template",
   "main": "expo-router/entry",
-  "version": "2.0.0",
+  "version": "2.1.0",
   "dependencies": {
     "expo": "~57.0.21",
     "expo-constants": "~57.0.17",

package/platform/base-url.js

@@ -0,0 +1,53 @@
+/**
+ * The subpath this app is served under, when the platform is serving it.
+ *
+ * WHY THIS EXISTS
+ *
+ * The preview is embedded in the control plane as a SAME-ORIGIN iframe
+ * (ADR-033), served under `/api/v1/preview/<appId>/`. Same-origin is not
+ * incidental: the canvas reads this app's DOM directly to measure controls,
+ * observe presses and detect readiness (ADR-039), and all three throw across
+ * origins. So the app cannot be given its own origin to escape the prefix —
+ * it has to be told the prefix instead.
+ *
+ * expo-router resolves routes against `window.location.pathname`. Without a
+ * base it compares that whole prefixed path against the route files and
+ * matches nothing, so EVERY screen — the entry one included — renders
+ * "Unmatched Route". Verified live before this existed.
+ *
+ * ON `experiments`
+ *
+ * `experiments.baseUrl` is Expo's only mechanism for subpath hosting, and it
+ * is typed and documented in @expo/config-types ("Export a website relative
+ * to a subpath of a domain"). This project already depends on that namespace
+ * — `typedRoutes` in app.json — which in Expo is a grab-bag of build-pipeline
+ * flags rather than a staging area.
+ *
+ * The exposure is a rename on an SDK upgrade. The symptom is unmistakable
+ * (every route renders "Unmatched Route") and the fix is this one field;
+ * check @expo/config-types' ExpoConfig for where it moved.
+ */
+
+/**
+ * Empty unless the platform set it. An app run directly (`npm run web`) has
+ * no prefix and serves at the origin root, which is what an empty base means.
+ * The variable is set by the harness when it starts Metro, from the pod's own
+ * app id — never written into the workspace, because the base URL is a
+ * deployment fact the platform owns and app.json belongs to you.
+ */
+function resolveBaseUrl() {
+  return process.env.EXPO_BASE_URL || '';
+}
+
+/** Applies the base to an Expo config, leaving everything else untouched. */
+function withPlatformBaseUrl(config) {
+  return {
+    ...config,
+    experiments: {
+      ...config.experiments,
+      baseUrl: resolveBaseUrl(),
+    },
+  };
+}
+
+module.exports = { resolveBaseUrl, withPlatformBaseUrl };