@radhya/mach 2.6.5 → 2.6.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -3
- package/dist/index.js +130 -130
- package/docs/deep-links.md +16 -2
- package/package.json +1 -1
package/docs/deep-links.md
CHANGED
|
@@ -32,12 +32,20 @@ Precedence is:
|
|
|
32
32
|
command flags > existing deepLinks config > profile-specific config > root mach.config.json > Expo config inference > prompts/defaults
|
|
33
33
|
```
|
|
34
34
|
|
|
35
|
-
For
|
|
35
|
+
For a linked project using Mach Web Hosting, this is enough:
|
|
36
36
|
|
|
37
37
|
```bash
|
|
38
|
-
mach deeplink setup
|
|
38
|
+
mach deeplink setup
|
|
39
39
|
```
|
|
40
40
|
|
|
41
|
+
Setup presents only stable deep-link hosts: the Mach Production address
|
|
42
|
+
(`project.getmach.dev`), then any active Production customer domain, followed
|
|
43
|
+
by a manual URL option. It does not offer Staging or immutable preview URLs.
|
|
44
|
+
Use `--base-url` when the app is hosted elsewhere or when you need an explicit
|
|
45
|
+
override. The chosen hostname is compiled into the native app; select a new
|
|
46
|
+
host later only when you are ready to run setup again and ship a new native
|
|
47
|
+
build.
|
|
48
|
+
|
|
41
49
|
Use `--profile` when the team/app metadata lives under a non-production submit profile:
|
|
42
50
|
|
|
43
51
|
```bash
|
|
@@ -74,6 +82,12 @@ mach deeplink setup \
|
|
|
74
82
|
|
|
75
83
|
When `--output` is not provided, Mach uses `public` if that folder exists; otherwise it writes to `deep-links` and prints a hosting note.
|
|
76
84
|
|
|
85
|
+
When you deploy with `mach web deploy`, Mach adds these association files to the
|
|
86
|
+
finished web output automatically. This works even when the web exporter writes
|
|
87
|
+
to `dist` or `build/web` while deep-link setup wrote files under `public` or
|
|
88
|
+
`deep-links`. The generated files replace stale association files in the upload,
|
|
89
|
+
so the hosted release matches `mach.config.json`.
|
|
90
|
+
|
|
77
91
|
`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:
|
|
78
92
|
|
|
79
93
|
```json
|