@yorun-ai/vrpc 0.9.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/CONTRIBUTING.md +82 -0
- package/LICENSE +201 -0
- package/README.md +232 -0
- package/README.zh-CN.md +231 -0
- package/dist/client.cjs +462 -0
- package/dist/client.d.cts +247 -0
- package/dist/client.d.ts +247 -0
- package/dist/client.es.js +442 -0
- package/dist/http.cjs +69 -0
- package/dist/http.d.cts +100 -0
- package/dist/http.d.ts +100 -0
- package/dist/http.es.js +64 -0
- package/dist/request-options-2HZzkj4w.cjs +353 -0
- package/dist/request-options-disym648.js +288 -0
- package/docs/guides/axios.md +115 -0
- package/docs/guides/usage.md +259 -0
- package/docs/maintainers/architecture.md +47 -0
- package/docs/maintainers/protocol.md +135 -0
- package/docs/maintainers/releasing.md +92 -0
- package/package.json +65 -0
package/CONTRIBUTING.md
ADDED
|
@@ -0,0 +1,82 @@
|
|
|
1
|
+
# Contributing
|
|
2
|
+
|
|
3
|
+
This guide defines the development, verification, documentation, commit, and pull-request requirements for `@yorun-ai/vrpc`. Package maintainers must also follow the [release guide](docs/maintainers/releasing.md).
|
|
4
|
+
|
|
5
|
+
## Prerequisites
|
|
6
|
+
|
|
7
|
+
- Node.js 24.11 or later.
|
|
8
|
+
- pnpm 11.15.0, using the repository lockfile.
|
|
9
|
+
|
|
10
|
+
Install dependencies from the repository root:
|
|
11
|
+
|
|
12
|
+
```bash
|
|
13
|
+
pnpm install --frozen-lockfile
|
|
14
|
+
```
|
|
15
|
+
|
|
16
|
+
## Repository layout
|
|
17
|
+
|
|
18
|
+
- `src/contracts/`: public types and error contracts.
|
|
19
|
+
- `src/core/`: request orchestration and protocol adaptation.
|
|
20
|
+
- `src/protocol/`: vRPC paths, headers, envelopes, and wire conversion.
|
|
21
|
+
- `src/transports/`: runtime network I/O.
|
|
22
|
+
- `src/entrypoints/`: public package entrypoints.
|
|
23
|
+
- `test/`: behavioral, compatibility, and release tests.
|
|
24
|
+
- `docs/guides/`: user-facing guides.
|
|
25
|
+
- `docs/maintainers/`: architecture, protocol, and release documentation.
|
|
26
|
+
|
|
27
|
+
Read `AGENTS.md`, `README.md`, and the applicable documentation before changing behavior or public contracts.
|
|
28
|
+
|
|
29
|
+
## Development workflow
|
|
30
|
+
|
|
31
|
+
1. Keep each change focused and preserve compatibility unless a breaking change is explicitly intended.
|
|
32
|
+
2. Define or update public contracts before implementing behavior.
|
|
33
|
+
3. Keep network I/O inside transports and protocol-independent orchestration inside core.
|
|
34
|
+
4. Add or update tests for behavioral changes.
|
|
35
|
+
5. Update documentation whenever exports, types, defaults, headers, errors, or request behavior change.
|
|
36
|
+
6. Run the relevant checks before opening a pull request.
|
|
37
|
+
|
|
38
|
+
Run the required checks before opening a pull request:
|
|
39
|
+
|
|
40
|
+
```bash
|
|
41
|
+
pnpm type-check
|
|
42
|
+
pnpm test
|
|
43
|
+
pnpm fmt:check
|
|
44
|
+
pnpm lint
|
|
45
|
+
pnpm build
|
|
46
|
+
pnpm test:package
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Use these commands while developing:
|
|
50
|
+
|
|
51
|
+
```bash
|
|
52
|
+
pnpm test:watch
|
|
53
|
+
pnpm fmt
|
|
54
|
+
pnpm lint:fix
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
Do not commit generated `dist/` output or `node_modules/`.
|
|
58
|
+
|
|
59
|
+
## Documentation
|
|
60
|
+
|
|
61
|
+
Repository documentation is maintained in English. The root `README.zh-CN.md` provides a Chinese project overview and links to the canonical English guides. Keep both root README files synchronized when their shared content changes.
|
|
62
|
+
|
|
63
|
+
- Keep package overview and documentation navigation in `README.md` and `README.zh-CN.md`.
|
|
64
|
+
- Put task-oriented material for package users in `docs/guides/`.
|
|
65
|
+
- Put architecture, protocol, release, and other repository-maintenance material in `docs/maintainers/`.
|
|
66
|
+
- Keep protocol details in `docs/maintainers/protocol.md` instead of duplicating them in the architecture overview.
|
|
67
|
+
|
|
68
|
+
## Commits
|
|
69
|
+
|
|
70
|
+
Create focused commits that explain the purpose of the change. Avoid mixing unrelated cleanup with functional work. Before committing, inspect the diff and run `git diff --check` in addition to the applicable project checks.
|
|
71
|
+
|
|
72
|
+
## Pull requests
|
|
73
|
+
|
|
74
|
+
A pull request should include:
|
|
75
|
+
|
|
76
|
+
- The motivation and scope of the change.
|
|
77
|
+
- Any public API, compatibility, or protocol impact.
|
|
78
|
+
- Tests added or updated and the commands used to verify the change.
|
|
79
|
+
- Documentation updates, including both root README languages when applicable.
|
|
80
|
+
- Release notes or migration guidance when users need to take action.
|
|
81
|
+
|
|
82
|
+
Keep pull requests focused and list any intentionally excluded follow-up work.
|
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2026 Cartopeira Pte. Ltd.
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,232 @@
|
|
|
1
|
+
# @yorun-ai/vrpc
|
|
2
|
+
|
|
3
|
+
**English** | [简体中文](README.zh-CN.md)
|
|
4
|
+
|
|
5
|
+
Client runtime for Vine vRPC and generic HTTP requests.
|
|
6
|
+
|
|
7
|
+
Repository: [github.com/yorun-ai/vrpc-ts](https://github.com/yorun-ai/vrpc-ts)
|
|
8
|
+
|
|
9
|
+
## Stability
|
|
10
|
+
|
|
11
|
+
The package starts at `0.9.0`. It is ready for use, but versions below `1.0.0` do not guarantee a stable public API. Breaking API changes may be released in a new `0.x` minor version and will include migration guidance. Version `1.0.0` will mark the stable API commitment.
|
|
12
|
+
|
|
13
|
+
## Installation
|
|
14
|
+
|
|
15
|
+
```bash
|
|
16
|
+
pnpm add @yorun-ai/vrpc
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
## Entry points
|
|
20
|
+
|
|
21
|
+
- `@yorun-ai/vrpc` / `@yorun-ai/vrpc/client`: vRPC client, protocol helpers, shared transport, and types.
|
|
22
|
+
- `@yorun-ai/vrpc/http`: generic HTTP client.
|
|
23
|
+
|
|
24
|
+
## vRPC quick start
|
|
25
|
+
|
|
26
|
+
```ts
|
|
27
|
+
import { VrpcInvokeError, createVrpcClient, getClientInstanceId } from "@yorun-ai/vrpc";
|
|
28
|
+
|
|
29
|
+
const client = createVrpcClient({
|
|
30
|
+
prefixUrl: "https://api.example.com/invoke",
|
|
31
|
+
timeoutMs: 15_000,
|
|
32
|
+
suppressGlobalToast: false,
|
|
33
|
+
clientInfo: {
|
|
34
|
+
clientName: "demo.browser",
|
|
35
|
+
clientVersion: "1.0.0",
|
|
36
|
+
clientInstanceId: getClientInstanceId(),
|
|
37
|
+
},
|
|
38
|
+
});
|
|
39
|
+
|
|
40
|
+
client.use({
|
|
41
|
+
onError(error, context) {
|
|
42
|
+
if (context.options.suppressGlobalToast) {
|
|
43
|
+
return;
|
|
44
|
+
}
|
|
45
|
+
console.error(error);
|
|
46
|
+
},
|
|
47
|
+
});
|
|
48
|
+
|
|
49
|
+
const profile = await client.invoke<{ id: number; name: string }>({
|
|
50
|
+
serviceName: "user.UserService",
|
|
51
|
+
methodName: "getProfile",
|
|
52
|
+
params: { userId: 1 },
|
|
53
|
+
options: {
|
|
54
|
+
timeoutMs: 3_000,
|
|
55
|
+
suppressGlobalToast: true,
|
|
56
|
+
},
|
|
57
|
+
});
|
|
58
|
+
|
|
59
|
+
// An argument-free method accepts null or an empty object.
|
|
60
|
+
await client.invoke({
|
|
61
|
+
serviceName: "user.UserService",
|
|
62
|
+
methodName: "ping",
|
|
63
|
+
params: null,
|
|
64
|
+
});
|
|
65
|
+
|
|
66
|
+
try {
|
|
67
|
+
await client.invoke({
|
|
68
|
+
serviceName: "user.UserService",
|
|
69
|
+
methodName: "missing",
|
|
70
|
+
params: {},
|
|
71
|
+
});
|
|
72
|
+
} catch (error) {
|
|
73
|
+
if (error instanceof VrpcInvokeError) {
|
|
74
|
+
console.error(error.status, error.vrpcStatus, error.code, error.reason);
|
|
75
|
+
}
|
|
76
|
+
}
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
`traceMode` controls only the automatically generated `vrpc-trace` header; it does not change routing or `prefixUrl`. Use the default `"portal"` mode through Vine Portal, where the header contains only an id. For a direct connection to a vRPC service, set `traceMode: "direct"` so the runtime generates both an id and a span. Per-call `options.trace` overrides the generated value.
|
|
80
|
+
|
|
81
|
+
### Request options
|
|
82
|
+
|
|
83
|
+
```ts
|
|
84
|
+
type VrpcRequestOptions = {
|
|
85
|
+
headers?: HeadersInit;
|
|
86
|
+
timeoutMs?: number;
|
|
87
|
+
requestInit?: Omit<RequestInit, "method" | "body" | "headers">;
|
|
88
|
+
suppressGlobalToast?: boolean;
|
|
89
|
+
trace?: { id: string; span?: string };
|
|
90
|
+
wire?: VrpcMethodWireSpec;
|
|
91
|
+
};
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
- Create-time `suppressGlobalToast` is the default; a per-call `true` or `false` overrides it.
|
|
95
|
+
- `timeoutMs` is disabled by default; without it, the built-in transport creates no local timeout and sends no `vrpc-options`.
|
|
96
|
+
- `wire` is per-call only and never enters the HTTP payload.
|
|
97
|
+
- Argument-free methods accept both `params: null` and `params: {}`.
|
|
98
|
+
- The browser transport defaults to `credentials: "omit"`; use `requestInit.credentials` when cookies are needed.
|
|
99
|
+
|
|
100
|
+
## Automatic CBOR
|
|
101
|
+
|
|
102
|
+
The runtime has no built-in CBOR dependency. A method without `wire` always uses JSON and requires no codec. Generated clients attach a sparse wire schema when a method's arguments or result contain Binary:
|
|
103
|
+
|
|
104
|
+
```ts
|
|
105
|
+
import type { VrpcCborCodec, VrpcWireSchema } from "@yorun-ai/vrpc";
|
|
106
|
+
|
|
107
|
+
const uploadArguments: VrpcWireSchema = {
|
|
108
|
+
kind: "object",
|
|
109
|
+
fields: {
|
|
110
|
+
content: { kind: "binary" },
|
|
111
|
+
},
|
|
112
|
+
};
|
|
113
|
+
|
|
114
|
+
const cborCodec: VrpcCborCodec = {
|
|
115
|
+
encode: (value) => yourCborLibrary.encode(value),
|
|
116
|
+
decode: (bytes) => yourCborLibrary.decode(bytes),
|
|
117
|
+
};
|
|
118
|
+
|
|
119
|
+
const client = createVrpcClient({
|
|
120
|
+
prefixUrl: "https://api.example.com/invoke",
|
|
121
|
+
clientInfo: {
|
|
122
|
+
clientName: "demo.browser",
|
|
123
|
+
clientVersion: "1.0.0",
|
|
124
|
+
clientInstanceId: getClientInstanceId(),
|
|
125
|
+
},
|
|
126
|
+
cborCodec,
|
|
127
|
+
});
|
|
128
|
+
|
|
129
|
+
await client.invoke({
|
|
130
|
+
serviceName: "file.FileService",
|
|
131
|
+
methodName: "upload",
|
|
132
|
+
params: { content: new Uint8Array([1, 2, 3]) },
|
|
133
|
+
options: {
|
|
134
|
+
wire: { arguments: uploadArguments },
|
|
135
|
+
},
|
|
136
|
+
});
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
Automatic selection:
|
|
140
|
+
|
|
141
|
+
- `wire.arguments`: the request `content-type` is `application/vrpc+cbor`.
|
|
142
|
+
- `wire.result`: `accept` is `application/vrpc+cbor, application/vrpc+json`.
|
|
143
|
+
- Neither: JSON.
|
|
144
|
+
- Wire without `cborCodec` throws a configuration error before network I/O.
|
|
145
|
+
|
|
146
|
+
`VrpcWireSchema` supports Binary, nullable, list, object, and `Map<Int|string, T>`. Binary remains raw bytes in CBOR, while an integer-keyed `Record` becomes a real integer-keyed CBOR Map.
|
|
147
|
+
|
|
148
|
+
## Vine Header
|
|
149
|
+
|
|
150
|
+
Generated by the runtime:
|
|
151
|
+
|
|
152
|
+
```text
|
|
153
|
+
content-type: application/vrpc+json
|
|
154
|
+
accept: application/vrpc+json
|
|
155
|
+
vrpc-trace: id=<32hex>
|
|
156
|
+
vrpc-client: name=demo.browser,version=1.0.0,instanceId=<uuid>
|
|
157
|
+
vrpc-options: timeout=3000ms
|
|
158
|
+
```
|
|
159
|
+
|
|
160
|
+
Custom `headers` cannot override `accept`, `content-type`, or any `vrpc-*` header. An explicit `timeoutMs` controls both the local `AbortController` and `vrpc-options`.
|
|
161
|
+
|
|
162
|
+
## Generic HTTP client
|
|
163
|
+
|
|
164
|
+
```ts
|
|
165
|
+
import { createHttpClient } from "@yorun-ai/vrpc/http";
|
|
166
|
+
|
|
167
|
+
const http = createHttpClient({
|
|
168
|
+
prefixUrl: "https://api.example.com",
|
|
169
|
+
timeoutMs: 5_000,
|
|
170
|
+
});
|
|
171
|
+
|
|
172
|
+
const profile = await http.request<{ id: number }>({
|
|
173
|
+
path: "/users/me",
|
|
174
|
+
query: { withProfile: true },
|
|
175
|
+
options: {
|
|
176
|
+
requestInit: { credentials: "include" },
|
|
177
|
+
suppressGlobalToast: true,
|
|
178
|
+
},
|
|
179
|
+
});
|
|
180
|
+
|
|
181
|
+
await http.request({
|
|
182
|
+
path: "/users",
|
|
183
|
+
method: "POST",
|
|
184
|
+
json: { name: "Vine" },
|
|
185
|
+
});
|
|
186
|
+
```
|
|
187
|
+
|
|
188
|
+
HTTP interceptors read merged request configuration from `context.options`. `json` and `body` are mutually exclusive, and an empty response returns `null`.
|
|
189
|
+
|
|
190
|
+
## Protocol helpers
|
|
191
|
+
|
|
192
|
+
```ts
|
|
193
|
+
import {
|
|
194
|
+
buildVrpcHeaders,
|
|
195
|
+
buildVrpcPath,
|
|
196
|
+
buildVrpcRequestBody,
|
|
197
|
+
generateVrpcId,
|
|
198
|
+
} from "@yorun-ai/vrpc";
|
|
199
|
+
|
|
200
|
+
const headers = buildVrpcHeaders({
|
|
201
|
+
clientInfo: {
|
|
202
|
+
clientName: "demo.browser",
|
|
203
|
+
clientVersion: "1.0.0",
|
|
204
|
+
clientInstanceId: getClientInstanceId(),
|
|
205
|
+
},
|
|
206
|
+
trace: { id: generateVrpcId() },
|
|
207
|
+
timeoutMs: 3_000,
|
|
208
|
+
});
|
|
209
|
+
|
|
210
|
+
const path = buildVrpcPath("user.UserService", "getProfile");
|
|
211
|
+
const body = buildVrpcRequestBody({ userId: 1 });
|
|
212
|
+
```
|
|
213
|
+
|
|
214
|
+
## Documentation
|
|
215
|
+
|
|
216
|
+
User guides:
|
|
217
|
+
|
|
218
|
+
- [Usage](./docs/guides/usage.md): HTTP/vRPC client configuration and extension points.
|
|
219
|
+
- [Axios integration](./docs/guides/axios.md): custom Axios transport and JSON protocol helpers.
|
|
220
|
+
|
|
221
|
+
Maintainer documentation:
|
|
222
|
+
|
|
223
|
+
- [Architecture](./docs/maintainers/architecture.md): module boundaries and request flow.
|
|
224
|
+
- [vRPC protocol](./docs/maintainers/protocol.md): paths, envelopes, headers, content negotiation, wire schemas, and generated-client requirements.
|
|
225
|
+
- [Releasing](./docs/maintainers/releasing.md): version management and npm publishing.
|
|
226
|
+
- [Contributing](./CONTRIBUTING.md): development, testing, documentation, commit, and pull-request workflow.
|
|
227
|
+
|
|
228
|
+
The root README and `docs/guides/` are for package users. `docs/maintainers/` is for repository maintainers and integrators implementing transports or code generation. Changes to public exports, types, defaults, headers, errors, or request behavior must be reflected in both the user-facing and maintainer documentation.
|
|
229
|
+
|
|
230
|
+
## License
|
|
231
|
+
|
|
232
|
+
This project is licensed under the [Apache License 2.0](./LICENSE).
|