@plitzi/sdk-server 0.35.9 → 0.35.10

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # @plitzi/sdk-server
 
+## 0.35.10
+
+### Patch Changes
+
+- **Breaking:** the space setting that lets a published site open the dev tools is now `settings.debugMode`, and
+  `settings.devTools` is gone.
+
+  It was always the same decision the SDK and the page server call `debugMode` — whether the dev-tools panel is
+  authorized — and having a third name for it invited confusing it with `devMode`, which is a different thing: it turns a
+  deployment into a development server (the unminified bundles, request timings, and the full action trace with every
+  step's results). A space can authorize debugging for its own site; it can never make its server a development one.
+
+  A space that stored `settings.devTools` needs it moved to `settings.debugMode`; nothing reads the old key.
+
+- Updated dependencies
+  - @plitzi/plitzi-sdk@0.35.10
+  - @plitzi/sdk-shared@0.35.10
+
 ## 0.35.9
 
 ### Patch Changes

package/dist/helpers/debugAuthorization.d.ts

@@ -3,13 +3,13 @@ type DebugConfig = {
     debugMode?: boolean;
     devMode?: boolean;
 };
-type DebugSettings = Pick<Schema['settings'], 'devTools'> | undefined;
+type DebugSettings = Pick<Schema['settings'], 'debugMode'> | undefined;
 /**
  * Whether a page — and what its flows did — may be debugged. One rule for the render and for every run it reports.
  *
  * The server decides first, through `debugMode`: set, it speaks for every space, and `false` is a refusal no space can
  * turn around. Left unset, a development server authorizes it, and so does a space whose own settings switched
- * `devTools` on. The settings are what this server loaded, never anything the request carries.
+ * `debugMode` on. The settings are what this server loaded, never anything the request carries.
  *
  * A page nobody authorized is told nothing: not the steps behind it, not even that a flow ran.
  */

package/dist/helpers/debugAuthorization.js

@@ -4,11 +4,11 @@
 *
 * The server decides first, through `debugMode`: set, it speaks for every space, and `false` is a refusal no space can
 * turn around. Left unset, a development server authorizes it, and so does a space whose own settings switched
-* `devTools` on. The settings are what this server loaded, never anything the request carries.
+* `debugMode` on. The settings are what this server loaded, never anything the request carries.
 *
 * A page nobody authorized is told nothing: not the steps behind it, not even that a flow ran.
 */
-var authorizesDebugging = (config, settings) => config.debugMode ?? (config.devMode === true || settings?.devTools === true);
+var authorizesDebugging = (config, settings) => config.debugMode ?? (config.devMode === true || settings?.debugMode === true);
 /**
 * The same rule, for a request that has not loaded the space yet.
 *

package/dist/modules/ssr/prepareRender.js

@@ -62,7 +62,7 @@ var prepareRender = async (req, config, spaceId, environment, revision, pluginMa
 	* product from the same cookie on its first pass, so the markup it hydrates matches.
 	*
 	* Who may authorize it: the server first, through `debugMode`. When it said nothing, a development server does, and
-	* so does the space itself (`settings.devTools`) — an owner inspecting their own published site. The space is read
+	* so does the space itself (`settings.debugMode`) — an owner inspecting their own published site. The space is read
 	* from what this server loaded, never from the request, so a visitor has no say in it.
 	*/
 	const debugAuthorized = !Boolean(req.query["__pt"]) && authorizesDebugging(config, schema?.settings);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plitzi/sdk-server",
-  "version": "0.35.9",
+  "version": "0.35.10",
   "license": "AGPL-3.0",
   "files": [
     "dist",
@@ -58,8 +58,8 @@
   "type": "module",
   "sideEffects": false,
   "dependencies": {
-    "@plitzi/plitzi-sdk": "0.35.9",
-    "@plitzi/sdk-shared": "0.35.9",
+    "@plitzi/plitzi-sdk": "0.35.10",
+    "@plitzi/sdk-shared": "0.35.10",
     "ejs": "^6.0.1",
     "esbuild": "^0.28.2",
     "jsonwebtoken": "^9.0.3",