@plitzi/sdk-variables 0.35.8 → 0.35.10
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/CHANGELOG.md +40 -0
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,45 @@
|
|
|
1
1
|
# @plitzi/sdk-variables
|
|
2
2
|
|
|
3
|
+
## 0.35.10
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- **Breaking:** the space setting that lets a published site open the dev tools is now `settings.debugMode`, and
|
|
8
|
+
`settings.devTools` is gone.
|
|
9
|
+
|
|
10
|
+
It was always the same decision the SDK and the page server call `debugMode` — whether the dev-tools panel is
|
|
11
|
+
authorized — and having a third name for it invited confusing it with `devMode`, which is a different thing: it turns a
|
|
12
|
+
deployment into a development server (the unminified bundles, request timings, and the full action trace with every
|
|
13
|
+
step's results). A space can authorize debugging for its own site; it can never make its server a development one.
|
|
14
|
+
|
|
15
|
+
A space that stored `settings.devTools` needs it moved to `settings.debugMode`; nothing reads the old key.
|
|
16
|
+
|
|
17
|
+
- Updated dependencies
|
|
18
|
+
- @plitzi/sdk-shared@0.35.10
|
|
19
|
+
|
|
20
|
+
## 0.35.9
|
|
21
|
+
|
|
22
|
+
### Patch Changes
|
|
23
|
+
|
|
24
|
+
- Debug a server action's whole flow from the dev-tools, not just its answer.
|
|
25
|
+
|
|
26
|
+
A run now reports an OUTLINE of what it did: every step in order, with its task, how it ended, how long it took, and
|
|
27
|
+
the redacted error of the one that broke the flow — the compensation steps `flow.onFailure` ran included. It carries
|
|
28
|
+
nothing a step was given or returned, so it goes to any page whose debugging the deployment authorized (`devMode`, or
|
|
29
|
+
a space that switched dev tools on for its published site) and to no other. The full trace, with each step's results,
|
|
30
|
+
still reaches only an authoring request or a development server.
|
|
31
|
+
|
|
32
|
+
Runs the SERVER started while rendering a page — the ones feeding `runtime: 'server'` elements — reach the dev-tools
|
|
33
|
+
too, seeded into the page and added to by every `/_rsc` refresh, under the same authorization: a page nobody
|
|
34
|
+
authorized is not told they happened. A response carrying them is never cached. A run that died on its deadline now
|
|
35
|
+
reports the step it was on rather than nothing at all.
|
|
36
|
+
|
|
37
|
+
The Actions tab was rebuilt around it: filters and search over the log, a run list that names the step that broke,
|
|
38
|
+
and a detail panel with the flow's timeline, its compensation shown apart, and what the run carried in and out.
|
|
39
|
+
|
|
40
|
+
- Updated dependencies
|
|
41
|
+
- @plitzi/sdk-shared@0.35.9
|
|
42
|
+
|
|
3
43
|
## 0.35.8
|
|
4
44
|
|
|
5
45
|
### Patch Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@plitzi/sdk-variables",
|
|
3
|
-
"version": "0.35.
|
|
3
|
+
"version": "0.35.10",
|
|
4
4
|
"license": "AGPL-3.0",
|
|
5
5
|
"files": [
|
|
6
6
|
"dist"
|
|
@@ -152,7 +152,7 @@
|
|
|
152
152
|
},
|
|
153
153
|
"dependencies": {
|
|
154
154
|
"@plitzi/plitzi-ui": "^1.6.21",
|
|
155
|
-
"@plitzi/sdk-shared": "0.35.
|
|
155
|
+
"@plitzi/sdk-shared": "0.35.10",
|
|
156
156
|
"clsx": "^2.1.1",
|
|
157
157
|
"zod": "^4.6.4"
|
|
158
158
|
},
|