@fabr-client/core 1.0.8 → 1.0.10-beta.0
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 +89 -83
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -17,12 +17,18 @@ fabr-client login --server https://pivot.enclaws.com --pairing-code <code>
|
|
|
17
17
|
fabr-client run
|
|
18
18
|
```
|
|
19
19
|
|
|
20
|
+
`fabr-client run` hides routine `Info` diagnostics from the terminal by
|
|
21
|
+
default while retaining `Warn` and `Error` output. Use
|
|
22
|
+
`fabr-client run --verbose` to show the full terminal log stream. The
|
|
23
|
+
`--once` and `--verbose` options can be combined.
|
|
24
|
+
|
|
20
25
|
## Local Diagnostics
|
|
21
26
|
|
|
22
27
|
While `fabr-client run` is active, key Connector diagnostics are also persisted
|
|
23
28
|
under the state root selected by the resolved config file. Active JSONL files
|
|
24
29
|
rotate at `100 MiB` or a UTC date boundary, are archived as ZIP files, and use a
|
|
25
|
-
`2 GiB` stable-state retention limit.
|
|
30
|
+
`2 GiB` stable-state retention limit. Terminal filtering does not affect these
|
|
31
|
+
local diagnostic files.
|
|
26
32
|
|
|
27
33
|
Generate a local diagnostic bundle with:
|
|
28
34
|
|
|
@@ -36,11 +42,11 @@ cannot be resolved, prints the final absolute path and size, and does not upload
|
|
|
36
42
|
the bundle to a server.
|
|
37
43
|
|
|
38
44
|
The main package is a thin launcher. It installs the matching native payload
|
|
39
|
-
through platform-specific optional dependencies, so end users only need the one
|
|
40
|
-
global install command above. Each platform payload contains `bin/fabr-client`
|
|
41
|
-
plus the managed Codex Runtime payload under `bin/runtime/`. The official Codex
|
|
42
|
-
entrypoint is `bin/runtime/bin/codex` (`.exe` on Windows), and helper
|
|
43
|
-
binaries/resources from the official platform release are bundled with it.
|
|
45
|
+
through platform-specific optional dependencies, so end users only need the one
|
|
46
|
+
global install command above. Each platform payload contains `bin/fabr-client`
|
|
47
|
+
plus the managed Codex Runtime payload under `bin/runtime/`. The official Codex
|
|
48
|
+
entrypoint is `bin/runtime/bin/codex` (`.exe` on Windows), and helper
|
|
49
|
+
binaries/resources from the official platform release are bundled with it.
|
|
44
50
|
|
|
45
51
|
## Platform Support
|
|
46
52
|
|
|
@@ -68,88 +74,88 @@ Use `latest` only for stable production versions such as `0.1.19`. Use
|
|
|
68
74
|
prerelease versions for test channels, for example `0.1.19-beta.0` or
|
|
69
75
|
`0.1.19-rc.0`.
|
|
70
76
|
|
|
71
|
-
For maintainers, build the Windows payload with PowerShell:
|
|
72
|
-
|
|
73
|
-
```powershell
|
|
74
|
-
pwsh ./scripts/package-fabr-client.ps1 `
|
|
75
|
-
-Profile release `
|
|
76
|
-
-PackNpm `
|
|
77
|
-
-CodexRuntimeMode official `
|
|
78
|
-
-CodexRuntimeVersion 0.
|
|
79
|
-
```
|
|
80
|
-
|
|
81
|
-
On macOS, build both `darwin-x64` and `darwin-arm64` payloads:
|
|
77
|
+
For maintainers, build the Windows payload with PowerShell:
|
|
78
|
+
|
|
79
|
+
```powershell
|
|
80
|
+
pwsh ./scripts/package-fabr-client.ps1 `
|
|
81
|
+
-Profile release `
|
|
82
|
+
-PackNpm `
|
|
83
|
+
-CodexRuntimeMode official `
|
|
84
|
+
-CodexRuntimeVersion 0.153.2
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
On macOS, build both `darwin-x64` and `darwin-arm64` payloads:
|
|
82
88
|
|
|
83
89
|
```bash
|
|
84
|
-
./scripts/package-macos-all.sh \
|
|
85
|
-
--profile release \
|
|
86
|
-
--pack-npm \
|
|
87
|
-
--codex-runtime-mode official \
|
|
88
|
-
--codex-runtime-version 0.
|
|
89
|
-
```
|
|
90
|
-
|
|
91
|
-
On Linux ARM64, build the `linux-arm64` payload on an ARM64 Linux build host:
|
|
90
|
+
./scripts/package-macos-all.sh \
|
|
91
|
+
--profile release \
|
|
92
|
+
--pack-npm \
|
|
93
|
+
--codex-runtime-mode official \
|
|
94
|
+
--codex-runtime-version 0.153.2
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
On Linux ARM64, build the `linux-arm64` payload on an ARM64 Linux build host:
|
|
92
98
|
|
|
93
99
|
```bash
|
|
94
100
|
./scripts/package-fabr-client.sh \
|
|
95
|
-
--profile release \
|
|
96
|
-
--target aarch64-unknown-linux-gnu \
|
|
97
|
-
--pack-npm \
|
|
98
|
-
--codex-runtime-mode official \
|
|
99
|
-
--codex-runtime-version 0.
|
|
100
|
-
```
|
|
101
|
-
|
|
102
|
-
On Linux x64, build the `linux-x64` payload on an x86_64 Linux build host:
|
|
103
|
-
|
|
104
|
-
```bash
|
|
105
|
-
./scripts/package-linux-x64.sh \
|
|
106
|
-
--profile release \
|
|
107
|
-
--pack-npm \
|
|
108
|
-
--codex-runtime-mode official \
|
|
109
|
-
--codex-runtime-version 0.
|
|
110
|
-
```
|
|
111
|
-
|
|
112
|
-
Offline packaging can use a local official platform archive:
|
|
113
|
-
|
|
114
|
-
```bash
|
|
115
|
-
./scripts/package-linux-x64.sh \
|
|
116
|
-
--profile release \
|
|
117
|
-
--pack-npm \
|
|
118
|
-
--codex-runtime-mode official \
|
|
119
|
-
--codex-runtime-version 0.
|
|
120
|
-
--codex-runtime-release-file-linux-x64 /path/to/codex-0.
|
|
121
|
-
```
|
|
122
|
-
|
|
123
|
-
```bash
|
|
124
|
-
./scripts/package-fabr-client.sh \
|
|
125
|
-
--profile release \
|
|
126
|
-
--target aarch64-unknown-linux-gnu \
|
|
127
|
-
--pack-npm \
|
|
128
|
-
--codex-runtime-mode official \
|
|
129
|
-
--codex-runtime-version 0.
|
|
130
|
-
--codex-runtime-release-file /path/to/codex-0.
|
|
131
|
-
```
|
|
132
|
-
|
|
133
|
-
macOS offline packaging requires separate release archives per architecture:
|
|
134
|
-
|
|
135
|
-
```bash
|
|
136
|
-
./scripts/package-macos-all.sh \
|
|
137
|
-
--profile release \
|
|
138
|
-
--pack-npm \
|
|
139
|
-
--codex-runtime-mode official \
|
|
140
|
-
--codex-runtime-version 0.
|
|
141
|
-
--codex-runtime-release-file-darwin-x64 /path/to/codex-0.
|
|
142
|
-
--codex-runtime-release-file-darwin-arm64 /path/to/codex-0.
|
|
143
|
-
```
|
|
144
|
-
|
|
145
|
-
For local debugging, maintainers can still use `staged` with a raw executable
|
|
146
|
-
or `build` with a local `codex-runtime` checkout:
|
|
147
|
-
|
|
148
|
-
```powershell
|
|
149
|
-
pwsh ./scripts/package-fabr-client.ps1 -Profile release -PackNpm -CodexRuntimeMode staged -CodexRuntimeBin C:\path\to\codex.exe
|
|
150
|
-
```
|
|
151
|
-
|
|
152
|
-
## Release Artifact Manifest
|
|
101
|
+
--profile release \
|
|
102
|
+
--target aarch64-unknown-linux-gnu \
|
|
103
|
+
--pack-npm \
|
|
104
|
+
--codex-runtime-mode official \
|
|
105
|
+
--codex-runtime-version 0.153.2
|
|
106
|
+
```
|
|
107
|
+
|
|
108
|
+
On Linux x64, build the `linux-x64` payload on an x86_64 Linux build host:
|
|
109
|
+
|
|
110
|
+
```bash
|
|
111
|
+
./scripts/package-linux-x64.sh \
|
|
112
|
+
--profile release \
|
|
113
|
+
--pack-npm \
|
|
114
|
+
--codex-runtime-mode official \
|
|
115
|
+
--codex-runtime-version 0.153.2
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
Offline packaging can use a local official platform archive:
|
|
119
|
+
|
|
120
|
+
```bash
|
|
121
|
+
./scripts/package-linux-x64.sh \
|
|
122
|
+
--profile release \
|
|
123
|
+
--pack-npm \
|
|
124
|
+
--codex-runtime-mode official \
|
|
125
|
+
--codex-runtime-version 0.153.2 \
|
|
126
|
+
--codex-runtime-release-file-linux-x64 /path/to/codex-0.153.2-linux-x64.tgz
|
|
127
|
+
```
|
|
128
|
+
|
|
129
|
+
```bash
|
|
130
|
+
./scripts/package-fabr-client.sh \
|
|
131
|
+
--profile release \
|
|
132
|
+
--target aarch64-unknown-linux-gnu \
|
|
133
|
+
--pack-npm \
|
|
134
|
+
--codex-runtime-mode official \
|
|
135
|
+
--codex-runtime-version 0.153.2 \
|
|
136
|
+
--codex-runtime-release-file /path/to/codex-0.153.2-linux-arm64.tgz
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
macOS offline packaging requires separate release archives per architecture:
|
|
140
|
+
|
|
141
|
+
```bash
|
|
142
|
+
./scripts/package-macos-all.sh \
|
|
143
|
+
--profile release \
|
|
144
|
+
--pack-npm \
|
|
145
|
+
--codex-runtime-mode official \
|
|
146
|
+
--codex-runtime-version 0.153.2 \
|
|
147
|
+
--codex-runtime-release-file-darwin-x64 /path/to/codex-0.153.2-darwin-x64.tgz \
|
|
148
|
+
--codex-runtime-release-file-darwin-arm64 /path/to/codex-0.153.2-darwin-arm64.tgz
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
For local debugging, maintainers can still use `staged` with a raw executable
|
|
152
|
+
or `build` with a local `codex-runtime` checkout:
|
|
153
|
+
|
|
154
|
+
```powershell
|
|
155
|
+
pwsh ./scripts/package-fabr-client.ps1 -Profile release -PackNpm -CodexRuntimeMode staged -CodexRuntimeBin C:\path\to\codex.exe
|
|
156
|
+
```
|
|
157
|
+
|
|
158
|
+
## Release Artifact Manifest
|
|
153
159
|
|
|
154
160
|
Desktop installers consume versioned release artifacts and checksums instead of
|
|
155
161
|
importing source files from this repository. Place finalized payload archives in
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@fabr-client/core",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.10-beta.0",
|
|
4
4
|
"description": "Cross-platform launcher for Fabr Client",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"homepage": "https://pivot.enclaws.com",
|
|
@@ -19,11 +19,11 @@
|
|
|
19
19
|
"smoke": "node bin/fabr-client.js --help"
|
|
20
20
|
},
|
|
21
21
|
"optionalDependencies": {
|
|
22
|
-
"@fabr-client/core-win32-x64": "1.0.
|
|
23
|
-
"@fabr-client/core-darwin-x64": "1.0.
|
|
24
|
-
"@fabr-client/core-darwin-arm64": "1.0.
|
|
25
|
-
"@fabr-client/core-linux-arm64": "1.0.
|
|
26
|
-
"@fabr-client/core-linux-x64": "1.0.
|
|
22
|
+
"@fabr-client/core-win32-x64": "1.0.10-beta.0",
|
|
23
|
+
"@fabr-client/core-darwin-x64": "1.0.10-beta.0",
|
|
24
|
+
"@fabr-client/core-darwin-arm64": "1.0.10-beta.0",
|
|
25
|
+
"@fabr-client/core-linux-arm64": "1.0.10-beta.0",
|
|
26
|
+
"@fabr-client/core-linux-x64": "1.0.10-beta.0"
|
|
27
27
|
},
|
|
28
28
|
"files": [
|
|
29
29
|
"bin/",
|