@radhya/mach 2.6.5 → 2.6.7

package/docs/deep-links.md

@@ -32,12 +32,20 @@ Precedence is:
 command flags > existing deepLinks config > profile-specific config > root mach.config.json > Expo config inference > prompts/defaults
 ```
 
-For most linked projects, this is enough:
+For a linked project using Mach Web Hosting, this is enough:
 
 ```bash
-mach deeplink setup --base-url https://app.example.com
+mach deeplink setup
 ```
 
+Setup presents only stable deep-link hosts: the Mach Production address
+(`project.getmach.dev`), then any active Production customer domain, followed
+by a manual URL option. It does not offer Staging or immutable preview URLs.
+Use `--base-url` when the app is hosted elsewhere or when you need an explicit
+override. The chosen hostname is compiled into the native app; select a new
+host later only when you are ready to run setup again and ship a new native
+build.
+
 Use `--profile` when the team/app metadata lives under a non-production submit profile:
 
 ```bash
@@ -74,6 +82,12 @@ mach deeplink setup \
 
 When `--output` is not provided, Mach uses `public` if that folder exists; otherwise it writes to `deep-links` and prints a hosting note.
 
+When you deploy with `mach web deploy`, Mach adds these association files to the
+finished web output automatically. This works even when the web exporter writes
+to `dist` or `build/web` while deep-link setup wrote files under `public` or
+`deep-links`. The generated files replace stale association files in the upload,
+so the hosted release matches `mach.config.json`.
+
 `mach.config.json` is the only Mach deep-link source of truth. Values already available from the selected profile or root config are not duplicated inside `deepLinks`. A typical generated block is intentionally small:
 
 ```json
@@ -165,6 +179,27 @@ export default {
 }
 ```
 
+### Multi-app Expo workspaces
+
+When several separately shipped apps share one Expo `app.config.ts`, keep a **single workspace wrapper** and let it select the Mach config for the active build. Do not add one fixed plugin entry per product: every config plugin runs for every build, so a fixed Pocket entry could otherwise add Pocket links to another app.
+
+`mach deeplink setup` still writes each product’s association files and configuration when run from that product directory. It intentionally does not inject a fixed plugin into the shared Expo root. The wrapper chooses the config using the same environment variable that chooses the product:
+
+```js
+const withMach = require('@radhya/mach/expo-plugin')
+
+module.exports = (config) => {
+  const appKey = process.env.EXPO_PUBLIC_APP_KEY || 'main'
+  return withMach(config, {
+    machConfigPath: appKey === 'main'
+      ? 'mach.config.json'
+      : `apps/${appKey}/mach.config.json`,
+  })
+}
+```
+
+Put that wrapper once in the root `plugins` array. Each product’s build profile must set its own selector environment value. Mach resolves the parent Expo root and that profile environment during `mach deeplink verify`, so verification checks the same app configuration that the focused build uses.
+
 ## Flutter Projects
 
 For Flutter applications, setup makes conservative, idempotent native changes:

package/expo-plugin/index.js

@@ -40,11 +40,14 @@ const domainFromBaseUrl = value => {
   }
 }
 
-const readMachConfig = config => {
+const readMachConfig = (config, options = {}) => {
   const projectRoot = config && config._internal && config._internal.projectRoot
     ? config._internal.projectRoot
     : process.cwd()
-  const configPath = path.join(projectRoot, 'mach.config.json')
+  const configuredPath = nonEmpty(options && options.machConfigPath)
+  const configPath = configuredPath
+    ? path.resolve(projectRoot, configuredPath)
+    : path.join(projectRoot, 'mach.config.json')
   if (!fs.existsSync(configPath)) return {}
   return JSON.parse(fs.readFileSync(configPath, 'utf-8'))
 }
@@ -98,8 +101,8 @@ const hasDomainFilter = (filter, domain) => {
   return data.some(item => item && item.scheme === 'https' && item.host === domain)
 }
 
-const resolveDeepLinks = config => {
-  const machConfig = readMachConfig(config)
+const resolveDeepLinks = (config, options) => {
+  const machConfig = readMachConfig(config, options)
   const deepLinks = machConfig.deepLinks || {}
   const profileName = deepLinks.profile || process.env.MACH_PROFILE || process.env.EAS_BUILD_PROFILE || 'production'
   const profile = resolveBuildProfile(machConfig, profileName)
@@ -120,8 +123,8 @@ const resolveDeepLinks = config => {
   return { ...deepLinks, baseUrl, domain, scheme }
 }
 
-const resolveOta = config => {
-  const machConfig = readMachConfig(config)
+const resolveOta = (config, options) => {
+  const machConfig = readMachConfig(config, options)
   const ota = machConfig.ota || machConfig.update || {}
   if (ota.enabled === false) return { enabled: false }
   const projectId = nonEmpty(machConfig.projectId)
@@ -138,8 +141,8 @@ const resolveOta = config => {
   return { ...ota, enabled: Boolean(url), projectId, engine, url, runtimeVersion, runtimeVersionPolicy, channel }
 }
 
-const resolvePush = config => {
-  const machConfig = readMachConfig(config)
+const resolvePush = (config, options) => {
+  const machConfig = readMachConfig(config, options)
   const push = machConfig.push || {}
   const projectRoot = projectRootForConfig(config)
   return {
@@ -154,10 +157,10 @@ const resolvePush = config => {
   }
 }
 
-module.exports = function withMachDeepLinks(config) {
-  const deepLinks = resolveDeepLinks(config)
-  const ota = resolveOta(config)
-  const push = resolvePush(config)
+module.exports = function withMachDeepLinks(config, options) {
+  const deepLinks = resolveDeepLinks(config, options)
+  const ota = resolveOta(config, options)
+  const push = resolvePush(config, options)
 
   config.extra = { ...(config.extra || {}) }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@radhya/mach",
-  "version": "2.6.5",
+  "version": "2.6.7",
   "description": "Mach CLI: cloud build and delivery for Flutter, React Native, and Expo",
   "main": "dist/index.js",
   "type": "module",