waypoint-expo-template 2.1.0 → 3.0.0

package/.claude/settings.json

@@ -0,0 +1,5 @@
+{
+  "enabledPlugins": {
+    "expo@claude-plugins-official": true
+  }
+}

package/AGENTS.md

@@ -0,0 +1,3 @@
+# Expo HAS CHANGED
+
+Read the exact versioned docs at https://docs.expo.dev/versions/v57.0.0/ before writing any code.

package/App.tsx

@@ -0,0 +1,20 @@
+import { StatusBar } from 'expo-status-bar';
+import { StyleSheet, Text, View } from 'react-native';
+
+export default function App() {
+  return (
+    <View style={styles.container}>
+      <Text>Open up App.tsx to start working on your app!</Text>
+      <StatusBar style="auto" />
+    </View>
+  );
+}
+
+const styles = StyleSheet.create({
+  container: {
+    flex: 1,
+    backgroundColor: '#fff',
+    alignItems: 'center',
+    justifyContent: 'center',
+  },
+});

package/CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md

package/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2015-present 650 Industries, Inc. (aka Expo)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/app.json

@@ -4,39 +4,22 @@
     "slug": "waypoint-expo-template",
     "version": "1.0.0",
     "orientation": "portrait",
-    "icon": "./assets/images/icon.png",
-    "scheme": "waypointexpotemplate",
-    "userInterfaceStyle": "automatic",
+    "icon": "./assets/icon.png",
+    "userInterfaceStyle": "light",
     "ios": {
-      "icon": "./assets/expo.icon"
+      "supportsTablet": true
     },
     "android": {
       "adaptiveIcon": {
         "backgroundColor": "#E6F4FE",
-        "foregroundImage": "./assets/images/android-icon-foreground.png",
-        "backgroundImage": "./assets/images/android-icon-background.png",
-        "monochromeImage": "./assets/images/android-icon-monochrome.png"
+        "foregroundImage": "./assets/android-icon-foreground.png",
+        "backgroundImage": "./assets/android-icon-background.png",
+        "monochromeImage": "./assets/android-icon-monochrome.png"
       },
       "predictiveBackGestureEnabled": false
     },
     "web": {
-      "output": "static",
-      "favicon": "./assets/images/favicon.png"
-    },
-    "plugins": [
-      "expo-router",
-      [
-        "expo-splash-screen",
-        {
-          "backgroundColor": "#208AEF",
-          "image": "./assets/images/splash-icon.png",
-          "imageWidth": 76
-        }
-      ]
-    ],
-    "experiments": {
-      "typedRoutes": true,
-      "reactCompiler": true
+      "favicon": "./assets/favicon.png"
     }
   }
 }

package/index.ts

@@ -0,0 +1,8 @@
+import { registerRootComponent } from 'expo';
+
+import App from './App';
+
+// registerRootComponent calls AppRegistry.registerComponent('main', () => App);
+// It also ensures that whether you load the app in Expo Go or in a native build,
+// the environment is set up appropriately
+registerRootComponent(App);

package/package.json

@@ -1,22 +1,12 @@
 {
   "name": "waypoint-expo-template",
-  "main": "expo-router/entry",
-  "version": "2.1.0",
+  "version": "3.0.0",
+  "main": "index.ts",
   "dependencies": {
     "expo": "~57.0.21",
-    "expo-constants": "~57.0.17",
-    "expo-font": "~57.0.3",
-    "expo-linking": "~57.0.9",
-    "expo-router": "~57.0.20",
-    "expo-splash-screen": "~57.0.8",
     "expo-status-bar": "~57.0.1",
-    "expo-system-ui": "~57.0.3",
     "react": "19.2.3",
-    "react-dom": "19.2.3",
-    "react-native": "0.86.3",
-    "react-native-safe-area-context": "~5.7.0",
-    "react-native-screens": "~4.26.0",
-    "react-native-web": "~0.21.0"
+    "react-native": "0.86.3"
   },
   "devDependencies": {
     "@types/react": "~19.2.2",
@@ -28,5 +18,5 @@
     "ios": "expo start --ios",
     "web": "expo start --web"
   },
-  "description": "Expo app template for Waypoint app previews."
+  "description": "Expo app template for Waypoint app previews \u2014 create-expo-app blank-typescript, unmodified."
 }

package/tsconfig.json

@@ -1,20 +1,6 @@
 {
   "extends": "expo/tsconfig.base",
   "compilerOptions": {
-    "strict": true,
-    "paths": {
-      "@/*": [
-        "./src/*"
-      ],
-      "@/assets/*": [
-        "./assets/*"
-      ]
-    }
-  },
-  "include": [
-    "**/*.ts",
-    "**/*.tsx",
-    ".expo/types/**/*.ts",
-    "expo-env.d.ts"
-  ]
+    "strict": true
+  }
 }

package/README.md

@@ -1,45 +0,0 @@
-# waypoint-expo-template
-
-The Expo app that `bootstrap_app_cli` installs into a fresh workspace. It is a
-`create-expo-app` scaffold, reduced to the smallest thing that renders inside a
-Waypoint device-preview tile.
-
-## What is here
-
-```
-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
-declared screen list or control coordinates.
-
-The preview canvas derives its flow graph itself: screens come from the route
-files under `src/app`, positions are measured from the running app, and button
-presses are observed directly because the preview iframe is same-origin. The
-app is just an app. See ADR-039.
-
-## Adding a screen
-
-1. `src/app/<name>.tsx` — put a `testID` on every control that navigates
-2. add a `links` entry in `src/navigation.ts` for each of those controls
-3. `npx tsc --noEmit`
-
-There is no step 4. Nothing to compile, nothing to regenerate.

package/app.config.js

@@ -1,10 +0,0 @@
-// 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/assets/expo.icon/Assets/expo-symbol 2.svg

@@ -1,3 +0,0 @@
-<svg width="652" height="606" viewBox="0 0 652 606" fill="none" xmlns="http://www.w3.org/2000/svg">
-<path d="M353.554 0H298.446C273.006 0 249.684 14.6347 237.962 37.9539L4.37994 502.646C-1.04325 513.435 -1.45067 526.178 3.2716 537.313L22.6123 582.918C34.6475 611.297 72.5404 614.156 88.4414 587.885L309.863 222.063C313.34 216.317 319.439 212.826 326 212.826C332.561 212.826 338.659 216.317 342.137 222.063L563.559 587.885C579.46 614.156 617.352 611.297 629.388 582.918L648.728 537.313C653.451 526.178 653.043 513.435 647.62 502.646L414.038 37.9539C402.316 14.6347 378.994 0 353.554 0Z" fill="white"/>
-</svg>

package/assets/expo.icon/icon.json

@@ -1,40 +0,0 @@
-{
-  "fill" : {
-    "automatic-gradient" : "extended-srgb:0.00000,0.47843,1.00000,1.00000"
-  },
-  "groups" : [
-    {
-      "layers" : [
-        {
-          "image-name" : "expo-symbol 2.svg",
-          "name" : "expo-symbol 2",
-          "position" : {
-            "scale" : 1,
-            "translation-in-points" : [
-              1.1008400065293245e-05,
-              -16.046875
-            ]
-          }
-        },
-        {
-          "image-name" : "grid.png",
-          "name" : "grid"
-        }
-      ],
-      "shadow" : {
-        "kind" : "neutral",
-        "opacity" : 0.5
-      },
-      "translucency" : {
-        "enabled" : true,
-        "value" : 0.5
-      }
-    }
-  ],
-  "supported-platforms" : {
-    "circles" : [
-      "watchOS"
-    ],
-    "squares" : "shared"
-  }
-}

package/platform/base-url.js

@@ -1,53 +0,0 @@
-/**
- * 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 };

package/src/app/_layout.tsx

@@ -1,16 +0,0 @@
-import { Stack } from 'expo-router';
-
-/**
- * A plain Stack, deliberately.
- *
- * `create-expo-app` scaffolds a tab layout. A tab bar is wrong here: every
- * screen is rendered inside a device-preview tile on the canvas, and a
- * persistent tab bar would appear in all of them and offer a second way to
- * navigate that the flow graph knows nothing about.
- *
- * `headerShown: false` for the same reason — the canvas labels each tile
- * itself, so a header would be a duplicate title inside the device frame.
- */
-export default function RootLayout() {
-  return <Stack screenOptions={{ headerShown: false }} />;
-}

package/src/app/index.tsx

@@ -1,22 +0,0 @@
-import { StyleSheet, Text, View } from 'react-native';
-
-/**
- * The entry screen — `src/app/index.tsx` is `/` by expo-router's own
- * convention, which is also how the preview canvas knows it is the flow's
- * starting point. Nothing declares that.
- *
- * Replace this with the real first screen. Put a `testID` on any control that
- * navigates, and declare where it leads in `src/navigation.ts`.
- */
-export default function Index() {
-  return (
-    <View style={styles.container} testID="screen-index">
-      <Text style={styles.text}>Home</Text>
-    </View>
-  );
-}
-
-const styles = StyleSheet.create({
-  container: { flex: 1, alignItems: 'center', justifyContent: 'center', backgroundColor: '#ffffff' },
-  text: { fontSize: 18 },
-});

package/src/navigation.ts

@@ -1,34 +0,0 @@
-/**
- * Which control leads where — and nothing else.
- *
- * The screens themselves are NOT declared here. With file-based routing they
- * are the files under `src/app`: `index.tsx` is `/`, `settings.tsx` is
- * `/settings`, and the preview canvas reads that directly. Writing the list
- * down again would create a second copy that can disagree with the first.
- *
- * What the filesystem cannot show is which button leads where — that lives
- * inside a handler, and `router.push('/settings')` behind an async call is
- * not something anything can read statically. This file is that missing edge.
- *
- * Each entry:
- *   from  the screen the control is on   (its route id: `/` is `index`,
- *                                         `/user/settings` is `user-settings`)
- *   via   the control's `testID`         (must match the prop in the component)
- *   to    the screen it leads to
- *   label optional; names the edge on the canvas
- *
- * Declare links in the direction the user travels, INCLUDING back. A link
- * returning to an earlier screen is written plainly — the canvas materializes
- * the return frame itself. Do not add a duplicate "return" screen for it.
- *
- * Never declare where a control sits. Positions are measured from the running
- * app, so restyling a button needs no change here.
- */
-export const links: Array<{
-  from: string;
-  via: string;
-  to: string;
-  label?: string;
-}> = [
-  // { from: 'index', via: 'btn-open-settings', to: 'settings', label: 'Open settings' },
-];