@huaweidevtools/aishell-dsh-client-credentials 0.0.15 → 0.0.16
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/lib/client.js +8 -6
- package/lib/index.js +82 -53
- package/lib/types/client/CredentialRequestForm.d.ts +6 -8
- package/lib/types/client/credential-form-visibility.d.ts +8 -12
- package/lib/types/client/credential-status.d.ts +7 -8
- package/lib/types/client/huawei-mark.d.ts +6 -4
- package/lib/types/client/index.d.ts +4 -4
- package/lib/types/out-of-band/login.d.ts +12 -12
- package/lib/types/reconcile.d.ts +15 -12
- package/package.json +2 -2
package/lib/client.js
CHANGED
|
@@ -266,10 +266,12 @@ const CHIP_STYLE_KEY = `${PLUGIN_ID$1}/chip-hover`;
|
|
|
266
266
|
* a disposer that removes the tag, and the `data-plugin` markers so
|
|
267
267
|
* `removeOwnedStyles` can also reach it. The disposer is what makes a reload
|
|
268
268
|
* pick up an edited rule — the fiber tears down, the tag goes, and the next
|
|
269
|
-
* materialization writes the new text.
|
|
270
|
-
*
|
|
271
|
-
*
|
|
272
|
-
*
|
|
269
|
+
* materialization writes the new text.
|
|
270
|
+
*
|
|
271
|
+
* A module-level install guarded by an id cannot do that: the tag outlives the
|
|
272
|
+
* module because the loader sweeps only `data-plugin` tags, so the guard finds
|
|
273
|
+
* it on the next materialization and returns, and the page keeps the rule from
|
|
274
|
+
* before the edit for its whole life.
|
|
273
275
|
*
|
|
274
276
|
* Call once from `apply()`, not from the components: the rule is shared by
|
|
275
277
|
* both chips (they carry the same `CHIP_CLASS`), so one sheet serves them and
|
|
@@ -1934,8 +1936,8 @@ async function clearBothStores(t) {
|
|
|
1934
1936
|
* Read the credential prefills the host has in its environment.
|
|
1935
1937
|
*
|
|
1936
1938
|
* Failure is not an event: a host with nothing in its environment answers an
|
|
1937
|
-
* empty object, and a route that cannot be reached answers `{}` too
|
|
1938
|
-
*
|
|
1939
|
+
* empty object, and a route that cannot be reached answers `{}` too. A form
|
|
1940
|
+
* that starts empty is the ordinary case, so there is nothing to report.
|
|
1939
1941
|
*
|
|
1940
1942
|
* @returns the prefills, or an empty object.
|
|
1941
1943
|
*/
|
package/lib/index.js
CHANGED
|
@@ -1039,12 +1039,12 @@ const MAX_FORM_ROUNDS = 10;
|
|
|
1039
1039
|
*
|
|
1040
1040
|
* ## Why no instruction follows
|
|
1041
1041
|
*
|
|
1042
|
-
*
|
|
1043
|
-
*
|
|
1044
|
-
* a
|
|
1045
|
-
*
|
|
1046
|
-
*
|
|
1047
|
-
*
|
|
1042
|
+
* The message states the fact and stops. Adding "do not call auth again until
|
|
1043
|
+
* they say to" reads as a permission rule to be interpreted, and a model given
|
|
1044
|
+
* a rule it cannot evaluate narrates its uncertainty instead of acting: asked
|
|
1045
|
+
* to look again, it reasons about whether that counts as consent, and neither
|
|
1046
|
+
* retries nor explains. The fact is what the model needs; what follows from it
|
|
1047
|
+
* is its judgement.
|
|
1048
1048
|
*/
|
|
1049
1049
|
var CredentialEntryCancelled = class extends Error {
|
|
1050
1050
|
constructor() {
|
|
@@ -2368,15 +2368,15 @@ const MAX_BODY_BYTES = 8 * 1024;
|
|
|
2368
2368
|
* answer from the same endpoint (profile: `GET /v3/projects`, with the account
|
|
2369
2369
|
* name read best-effort from `/v3/auth/domains`).
|
|
2370
2370
|
*
|
|
2371
|
-
* ## Why
|
|
2371
|
+
* ## Why the shared verifier rather than a narrower call
|
|
2372
2372
|
*
|
|
2373
|
-
*
|
|
2374
|
-
*
|
|
2375
|
-
*
|
|
2376
|
-
* no visible project, while
|
|
2377
|
-
* "saved" for
|
|
2378
|
-
* that gap, and the project list it returns is
|
|
2379
|
-
* before planning a deployment.
|
|
2373
|
+
* The form's own question is "is this pair valid", and the answer has to agree
|
|
2374
|
+
* with the one the tools get — otherwise it accepts credentials the tools then
|
|
2375
|
+
* refuse. A narrower check would do exactly that: `/v3/projects` rejects a
|
|
2376
|
+
* credential with no visible project, while a domains-only call accepts it, so
|
|
2377
|
+
* the form would say "saved" for a pair that fails on the first real call. One
|
|
2378
|
+
* verifier removes that gap, and the project list it returns is what a caller
|
|
2379
|
+
* needs before planning a deployment anyway.
|
|
2380
2380
|
*
|
|
2381
2381
|
* ## The region
|
|
2382
2382
|
*
|
|
@@ -2413,10 +2413,32 @@ function jsonError(status, message) {
|
|
|
2413
2413
|
error: message
|
|
2414
2414
|
}, { status });
|
|
2415
2415
|
}
|
|
2416
|
-
/**
|
|
2416
|
+
/**
|
|
2417
|
+
* Read a bounded JSON object body, or throw a user-readable message.
|
|
2418
|
+
*
|
|
2419
|
+
* ## Why the bound is checked before the read finishes
|
|
2420
|
+
*
|
|
2421
|
+
* The body is drained first and measured after, which is the only order the
|
|
2422
|
+
* `Request` API allows: it exposes no streaming reader for a buffered route.
|
|
2423
|
+
* That means the bound cannot prevent the memory a large body costs — it stops
|
|
2424
|
+
* a hostile body from being *parsed* and from reaching any code that assumes a
|
|
2425
|
+
* credential, which is what it is for here. The transport's own request cap is
|
|
2426
|
+
* the memory bound; this one guards the next step.
|
|
2427
|
+
*
|
|
2428
|
+
* ## Why bytes and not `text.length`
|
|
2429
|
+
*
|
|
2430
|
+
* `text.length` counts UTF-16 code units, so a body of three-byte characters
|
|
2431
|
+
* measures a third of its real size and slips under a bound it should not. The
|
|
2432
|
+
* limit is stated in bytes, so it is compared in bytes.
|
|
2433
|
+
*
|
|
2434
|
+
* @param request - the buffered request.
|
|
2435
|
+
* @returns the parsed object.
|
|
2436
|
+
* @throws when the body is too large, is not JSON, or is not an object.
|
|
2437
|
+
*/
|
|
2417
2438
|
async function readJsonBody(request) {
|
|
2418
2439
|
const text = await request.text();
|
|
2419
|
-
|
|
2440
|
+
const bytes = new TextEncoder().encode(text).length;
|
|
2441
|
+
if (bytes > MAX_BODY_BYTES) throw new Error("Request body too large.");
|
|
2420
2442
|
let parsed;
|
|
2421
2443
|
try {
|
|
2422
2444
|
parsed = JSON.parse(text);
|
|
@@ -2509,7 +2531,17 @@ function createCredentialRoutes(deps) {
|
|
|
2509
2531
|
});
|
|
2510
2532
|
},
|
|
2511
2533
|
clear: () => {
|
|
2512
|
-
|
|
2534
|
+
try {
|
|
2535
|
+
clearCredentials(store);
|
|
2536
|
+
} catch (error) {
|
|
2537
|
+
const message = `Could not clear the stored credentials: ${error instanceof Error ? error.message : String(error)}`;
|
|
2538
|
+
recordStatus([{
|
|
2539
|
+
op: "set",
|
|
2540
|
+
path: ["lastError"],
|
|
2541
|
+
value: message
|
|
2542
|
+
}]);
|
|
2543
|
+
return Promise.resolve(jsonError(500, message));
|
|
2544
|
+
}
|
|
2513
2545
|
recordStatus([
|
|
2514
2546
|
{
|
|
2515
2547
|
op: "set",
|
|
@@ -2576,6 +2608,37 @@ function apply(ctx, config) {
|
|
|
2576
2608
|
ctx.logger.warn(error);
|
|
2577
2609
|
});
|
|
2578
2610
|
};
|
|
2611
|
+
/**
|
|
2612
|
+
* Answer one form request, named by the token in the body.
|
|
2613
|
+
*
|
|
2614
|
+
* The cancel and confirm routes differ only in which outcome they record, so
|
|
2615
|
+
* they share this. Both need the same three things, and each is a failure
|
|
2616
|
+
* this has to get right:
|
|
2617
|
+
*
|
|
2618
|
+
* - **The body is read defensively.** A malformed one earns a `400` rather
|
|
2619
|
+
* than an exception, so the browser always receives JSON it can render.
|
|
2620
|
+
* - **The token decides which request is answered.** The browser can
|
|
2621
|
+
* deliver a stale answer after a reconnect, and settling whichever
|
|
2622
|
+
* request happens to be pending would end a form the person is looking
|
|
2623
|
+
* at — or, worse, tell a model the user declined something they did not.
|
|
2624
|
+
* - **An unmatched token is not an error.** The request it named is
|
|
2625
|
+
* already gone; there is nothing to do and the browser needs no message.
|
|
2626
|
+
*
|
|
2627
|
+
* @param kind - the outcome to record against the named request.
|
|
2628
|
+
* @returns the route handler.
|
|
2629
|
+
*/
|
|
2630
|
+
const settleByToken = (kind) => async (request) => {
|
|
2631
|
+
let body;
|
|
2632
|
+
try {
|
|
2633
|
+
body = await request.json();
|
|
2634
|
+
} catch {
|
|
2635
|
+
return jsonError(400, "Request body is not valid JSON.");
|
|
2636
|
+
}
|
|
2637
|
+
const token = body?.token;
|
|
2638
|
+
if (typeof token !== "string" || token === "") return jsonError(400, "token is required.");
|
|
2639
|
+
if (pendingForm !== void 0 && pendingForm.request.token === token) settleFormRequest({ kind }, pendingForm);
|
|
2640
|
+
return Response.json({ ok: true });
|
|
2641
|
+
};
|
|
2579
2642
|
/** Apply one batch of ops to the mirror. */
|
|
2580
2643
|
const mirrorOps = (ops) => {
|
|
2581
2644
|
for (const op of ops) if (op.path[0] === "credentialsStored") recordedStored = op.op === "set" && op.value === true;
|
|
@@ -2641,47 +2704,13 @@ function apply(ctx, config) {
|
|
|
2641
2704
|
path: CANCEL_PATH,
|
|
2642
2705
|
methods: ["POST"],
|
|
2643
2706
|
requestBody: "buffered",
|
|
2644
|
-
fetch:
|
|
2645
|
-
let body;
|
|
2646
|
-
try {
|
|
2647
|
-
body = await request.json();
|
|
2648
|
-
} catch {
|
|
2649
|
-
return Response.json({
|
|
2650
|
-
ok: false,
|
|
2651
|
-
error: "Request body is not valid JSON."
|
|
2652
|
-
}, { status: 400 });
|
|
2653
|
-
}
|
|
2654
|
-
const token = body?.token;
|
|
2655
|
-
if (typeof token !== "string" || token === "") return Response.json({
|
|
2656
|
-
ok: false,
|
|
2657
|
-
error: "token is required."
|
|
2658
|
-
}, { status: 400 });
|
|
2659
|
-
if (pendingForm !== void 0 && pendingForm.request.token === token) settleFormRequest({ kind: "cancelled" }, pendingForm);
|
|
2660
|
-
return Response.json({ ok: true });
|
|
2661
|
-
}
|
|
2707
|
+
fetch: settleByToken("cancelled")
|
|
2662
2708
|
}), "aishell-credentials: cancel route");
|
|
2663
2709
|
ctx.effect(() => ctx.connection.fetch.register({
|
|
2664
2710
|
path: CONFIRM_PATH,
|
|
2665
2711
|
methods: ["POST"],
|
|
2666
2712
|
requestBody: "buffered",
|
|
2667
|
-
fetch:
|
|
2668
|
-
let body;
|
|
2669
|
-
try {
|
|
2670
|
-
body = await request.json();
|
|
2671
|
-
} catch {
|
|
2672
|
-
return Response.json({
|
|
2673
|
-
ok: false,
|
|
2674
|
-
error: "Request body is not valid JSON."
|
|
2675
|
-
}, { status: 400 });
|
|
2676
|
-
}
|
|
2677
|
-
const token = body?.token;
|
|
2678
|
-
if (typeof token !== "string" || token === "") return Response.json({
|
|
2679
|
-
ok: false,
|
|
2680
|
-
error: "token is required."
|
|
2681
|
-
}, { status: 400 });
|
|
2682
|
-
if (pendingForm !== void 0 && pendingForm.request.token === token) settleFormRequest({ kind: "submitted" }, pendingForm);
|
|
2683
|
-
return Response.json({ ok: true });
|
|
2684
|
-
}
|
|
2713
|
+
fetch: settleByToken("submitted")
|
|
2685
2714
|
}), "aishell-credentials: confirm route");
|
|
2686
2715
|
ctx.effect(() => ctx.connection.fetch.register({
|
|
2687
2716
|
path: PREFILL_PATH,
|
|
@@ -15,19 +15,17 @@
|
|
|
15
15
|
* `aishell__auth`; `退出` clears the credential.
|
|
16
16
|
* - **Not signed in** — both ways to obtain a credential, side by side.
|
|
17
17
|
*
|
|
18
|
-
*
|
|
19
|
-
*
|
|
20
|
-
*
|
|
21
|
-
*
|
|
22
|
-
* and were replaced a moment later. One upright card with a button that reports
|
|
23
|
-
* its own state is both smaller and calmer.
|
|
18
|
+
* One panel with a button that reports its own state, rather than a page per
|
|
19
|
+
* step. The person sees one card either way, so separate pages would be the
|
|
20
|
+
* same layout repeated — and the transitions between them would be visible:
|
|
21
|
+
* fields appearing and being replaced a moment later as the probe answered.
|
|
24
22
|
*
|
|
25
23
|
* ## Why the browser route reports itself in place
|
|
26
24
|
*
|
|
27
25
|
* The button is the status: `checking` while the probe runs, `login` once it
|
|
28
26
|
* passes, `unsupported` when it fails, `cancel` while a login is in flight with
|
|
29
|
-
* the countdown beside it. A separate
|
|
30
|
-
* keep in step with
|
|
27
|
+
* the countdown beside it. A separate "waiting" page would be a second layout
|
|
28
|
+
* to keep in step with this one, for no gain.
|
|
31
29
|
*
|
|
32
30
|
* @module @huaweidevtools/aishell-dsh-client-credentials/client/CredentialRequestForm
|
|
33
31
|
*/
|
|
@@ -8,21 +8,17 @@
|
|
|
8
8
|
*
|
|
9
9
|
* ## One way the form comes up
|
|
10
10
|
*
|
|
11
|
-
* A chip opens it
|
|
12
|
-
*
|
|
13
|
-
* There used to be a second source — the Host publishing which session had a
|
|
14
|
-
* tool call blocked on credentials — and this module reconciled the two, with
|
|
15
|
-
* rules about which one owned the form and how a takeover republished the
|
|
16
|
-
* interaction. That request channel is gone: no tool call blocks on credentials
|
|
17
|
-
* any more, so a Host request cannot arrive, and every rule about outranking
|
|
18
|
-
* one describes a situation that cannot happen.
|
|
19
|
-
*
|
|
20
|
-
* The rules that remain are the ones a single door needs:
|
|
11
|
+
* A chip opens it, and that is the whole model. Every rule here exists to serve
|
|
12
|
+
* that single door:
|
|
21
13
|
*
|
|
22
14
|
* - An open while the form is already up is a no-op. Publishing a second
|
|
23
15
|
* interaction would remount the component and discard what was typed.
|
|
24
16
|
* - A close, or a dispose, withdraws it, and the ordinary composer comes back.
|
|
25
17
|
*
|
|
18
|
+
* No other producer exists, so no rule is needed for one. A second source would
|
|
19
|
+
* need rules about which owns the form and how a takeover republishes it — and
|
|
20
|
+
* those rules would be describing a situation the system cannot reach.
|
|
21
|
+
*
|
|
26
22
|
* ## Why a closure and not a class
|
|
27
23
|
*
|
|
28
24
|
* Written as a factory because the browser half is compiled by oxc, and a class
|
|
@@ -68,8 +64,8 @@ export interface CredentialFormVisibility {
|
|
|
68
64
|
* thing (one login at a time, one credential store), so publishing a
|
|
69
65
|
* second card would give two conversations a live form over one store.
|
|
70
66
|
* Moving the person to the card they already have is the honest answer,
|
|
71
|
-
* and it is
|
|
72
|
-
*
|
|
67
|
+
* and it is what keeps the chip alive across a conversation switch: the
|
|
68
|
+
* card is still on screen, just not in the conversation that was clicked.
|
|
73
69
|
*
|
|
74
70
|
* @param sessionId - the conversation the person is acting in.
|
|
75
71
|
*/
|
|
@@ -5,17 +5,16 @@
|
|
|
5
5
|
* presentation: the presence descriptor the Host reports, the verdict its route
|
|
6
6
|
* answers with, and the link to where a credential comes from.
|
|
7
7
|
*
|
|
8
|
-
* ## Why it
|
|
8
|
+
* ## Why it is its own module
|
|
9
9
|
*
|
|
10
|
-
*
|
|
11
|
-
*
|
|
12
|
-
* importing from
|
|
13
|
-
*
|
|
14
|
-
* form nor the chips owns. Same reasoning as `huawei-mark.ts`: the second
|
|
10
|
+
* Several modules need these — two chips and the form — and none of them owns
|
|
11
|
+
* the other. A shared contract belongs in a file that no consumer is the author
|
|
12
|
+
* of; importing it from one component would make that component's internals a
|
|
13
|
+
* public interface by accident. Same reasoning as `huawei-mark.ts`: the second
|
|
15
14
|
* consumer is when the shared part earns its own module.
|
|
16
15
|
*
|
|
17
|
-
* The paragraph that follows each is the contract the Host half
|
|
18
|
-
* is stated here because this file is
|
|
16
|
+
* The paragraph that follows each declaration is the contract the Host half
|
|
17
|
+
* implements; it is stated here because this file is where both sides read it.
|
|
19
18
|
*
|
|
20
19
|
* @module @huaweidevtools/aishell-dsh-client-credentials/client/credential-status
|
|
21
20
|
*/
|
|
@@ -34,10 +34,12 @@ export declare const CHIP_CLASS = "aishell-account-hint";
|
|
|
34
34
|
* a disposer that removes the tag, and the `data-plugin` markers so
|
|
35
35
|
* `removeOwnedStyles` can also reach it. The disposer is what makes a reload
|
|
36
36
|
* pick up an edited rule — the fiber tears down, the tag goes, and the next
|
|
37
|
-
* materialization writes the new text.
|
|
38
|
-
*
|
|
39
|
-
*
|
|
40
|
-
*
|
|
37
|
+
* materialization writes the new text.
|
|
38
|
+
*
|
|
39
|
+
* A module-level install guarded by an id cannot do that: the tag outlives the
|
|
40
|
+
* module because the loader sweeps only `data-plugin` tags, so the guard finds
|
|
41
|
+
* it on the next materialization and returns, and the page keeps the rule from
|
|
42
|
+
* before the edit for its whole life.
|
|
41
43
|
*
|
|
42
44
|
* Call once from `apply()`, not from the components: the rule is shared by
|
|
43
45
|
* both chips (they carry the same `CHIP_CLASS`), so one sheet serves them and
|
|
@@ -9,10 +9,10 @@
|
|
|
9
9
|
* verified account name come back through `ctx.configForms`, which the chips
|
|
10
10
|
* and the form read.
|
|
11
11
|
*
|
|
12
|
-
*
|
|
13
|
-
*
|
|
14
|
-
*
|
|
15
|
-
*
|
|
12
|
+
* The form is the one credential surface, and a chip click is what opens it.
|
|
13
|
+
* It renders in `conversation.composer`, and there is no Settings section
|
|
14
|
+
* beside it: one place to enter a credential means one place to look when none
|
|
15
|
+
* is working.
|
|
16
16
|
*
|
|
17
17
|
* @module @huaweidevtools/aishell-dsh-client-credentials/client
|
|
18
18
|
*/
|
|
@@ -12,18 +12,18 @@
|
|
|
12
12
|
* person there, wait for the cloud to post a credential back. That is
|
|
13
13
|
* {@link startBrowserLogin}, and it binds **its own** port.
|
|
14
14
|
*
|
|
15
|
-
* These
|
|
16
|
-
* a person takes their time:
|
|
17
|
-
*
|
|
18
|
-
* - **
|
|
19
|
-
* socket to answer its question and
|
|
20
|
-
* until someone clicked
|
|
21
|
-
*
|
|
22
|
-
* - **
|
|
23
|
-
* the port it was projected for and the service states how long it
|
|
24
|
-
* valid.
|
|
25
|
-
*
|
|
26
|
-
* sign-in nobody had begun.
|
|
15
|
+
* These are two operations rather than one, and merging them breaks in two
|
|
16
|
+
* ways that only show up when a person takes their time:
|
|
17
|
+
*
|
|
18
|
+
* - **A shared port would be held from the moment the card opened.** The
|
|
19
|
+
* probe binds a socket to answer its question and releases it immediately;
|
|
20
|
+
* a port kept until someone clicked would be held for as long as the page
|
|
21
|
+
* lived, by anyone who merely read the card.
|
|
22
|
+
* - **A login window would start before the person did.** The `login_url`
|
|
23
|
+
* names the port it was projected for and the service states how long it
|
|
24
|
+
* stays valid. Fixed at probe time, a card left open for a while would
|
|
25
|
+
* offer a URL that had already expired — and a countdown would run down on
|
|
26
|
+
* a sign-in nobody had begun.
|
|
27
27
|
*
|
|
28
28
|
* So each operation binds what it needs and releases it when its own job ends.
|
|
29
29
|
* The probe's port is closed as soon as the browser has answered; the login's
|
package/lib/types/reconcile.d.ts
CHANGED
|
@@ -1,19 +1,22 @@
|
|
|
1
1
|
/**
|
|
2
2
|
* Idempotent credential-status reconcile.
|
|
3
3
|
*
|
|
4
|
-
*
|
|
5
|
-
*
|
|
6
|
-
*
|
|
7
|
-
*
|
|
8
|
-
*
|
|
9
|
-
* ever re-read the store after boot either, so credentials written after boot
|
|
10
|
-
* (the env's `sync-hw-creds` writes them every minute) stayed invisible to the
|
|
11
|
-
* UI. Independent branches fix the former; the caller's timer and GET-route
|
|
12
|
-
* hook fix the latter.
|
|
4
|
+
* Derives `credentialsStored` and `accessKeyIdHint` from the store, and records
|
|
5
|
+
* only what changed. The two derivations are independent on purpose: a boot
|
|
6
|
+
* where the presence flag flips to true must still reach the branch that
|
|
7
|
+
* verifies and records the account name, or the chips show "unconfigured" until
|
|
8
|
+
* something else triggers a restart.
|
|
13
9
|
*
|
|
14
|
-
*
|
|
15
|
-
* is
|
|
16
|
-
*
|
|
10
|
+
* Nothing re-reads the store on its own, so a credential written while the
|
|
11
|
+
* process is running — the environment's `sync-hw-creds` writes them every
|
|
12
|
+
* minute — would stay invisible to the UI. The caller's timer and the GET
|
|
13
|
+
* route's hook provide those re-reads; this module only has to be safe to call
|
|
14
|
+
* repeatedly, which it is: at steady state it records nothing and verifies
|
|
15
|
+
* nothing.
|
|
16
|
+
*
|
|
17
|
+
* Kept as a factory — not inlined in `apply()` — so the whole decision table is
|
|
18
|
+
* drivable from a spec with a `MemoryBackend` and a fake verifier, never a real
|
|
19
|
+
* keyring or IAM call.
|
|
17
20
|
*
|
|
18
21
|
* @module @huaweidevtools/aishell-dsh-client-credentials/reconcile
|
|
19
22
|
*/
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@huaweidevtools/aishell-dsh-client-credentials",
|
|
3
3
|
"description": "AI Shell credentials — chip-opened web form for storing Huawei Cloud AK/SK in the credential store",
|
|
4
|
-
"version": "0.0.
|
|
4
|
+
"version": "0.0.16",
|
|
5
5
|
"publishConfig": {
|
|
6
6
|
"access": "public"
|
|
7
7
|
},
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
},
|
|
43
43
|
"license": "Apache-2.0",
|
|
44
44
|
"dependencies": {
|
|
45
|
-
"@huaweidevtools/aishell-dsh-credentials-store": "0.0.
|
|
45
|
+
"@huaweidevtools/aishell-dsh-credentials-store": "0.0.16"
|
|
46
46
|
},
|
|
47
47
|
"peerDependencies": {
|
|
48
48
|
"@deepseek-ai/cordis": "^4.0.4",
|