@hunsu/bridge 0.2.0-next.1 → 0.2.0-next.11
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 +14 -2
- package/dist/cli.js +409 -107
- package/dist/index.d.ts +25 -3
- package/dist/index.js +410 -108
- package/package.json +7 -4
package/README.md
CHANGED
|
@@ -12,15 +12,27 @@ npx @hunsu/bridge@next status
|
|
|
12
12
|
npx @hunsu/bridge@next open
|
|
13
13
|
```
|
|
14
14
|
|
|
15
|
+
Preview QA uses the same canonical package with an explicit durable profile:
|
|
16
|
+
|
|
17
|
+
```sh
|
|
18
|
+
npx @hunsu/bridge@candidate-next setup --profile preview
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
`production` is the default profile. A populated `HUNSU_HOME` cannot switch
|
|
22
|
+
profiles; use a clean QA OS user or home for preview. The installed service
|
|
23
|
+
persists the selected profile and ignores ambient Web and Connect endpoint
|
|
24
|
+
overrides.
|
|
25
|
+
|
|
15
26
|
The installed user service runs an exact package version from `HUNSU_HOME`, not
|
|
16
27
|
from the npm cache. Use `hunsu-bridge dev --port 0` for an isolated foreground
|
|
17
|
-
development daemon.
|
|
28
|
+
development daemon. Development mode may use explicit endpoint overrides;
|
|
29
|
+
installed daemons use only the profile endpoint allowlist.
|
|
18
30
|
|
|
19
31
|
For advanced local package verification only, run setup from an absolute
|
|
20
32
|
tarball path:
|
|
21
33
|
|
|
22
34
|
```sh
|
|
23
|
-
hunsu-bridge setup --runtime-package /absolute/path/hunsu-bridge-0.2.0-next.
|
|
35
|
+
hunsu-bridge setup --runtime-package /absolute/path/hunsu-bridge-0.2.0-next.11.tgz
|
|
24
36
|
```
|
|
25
37
|
|
|
26
38
|
This option rejects URLs, dist-tags, ranges, Git specs, relative paths, and
|