@notionhq/custom-blocks 0.1.28 → 0.1.29

package/dist/bridge/loadManifest.d.ts

@@ -11,7 +11,8 @@ export type ManifestLoadResult = {
 };
 /**
  * On the literal `localhost` hostname, attempts to load the custom block's optional self-hosted
- * manifest exposed by the worker dev shell at `/manifest`.
+ * manifest exposed by the worker dev shell, requested at the page-relative `manifest` path so
+ * blocks served from a subpath resolve it against their own base.
  *
  * It is up to the host to decide whether to use this manifest or provide its own persisted manifest.
  */

package/dist/bridge/loadManifest.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"loadManifest.d.ts","sourceRoot":"","sources":["../../../../home/runner/work/custom-blocks/custom-blocks/sdk/src/bridge/loadManifest.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,4CAA4C,CAAA;AACtF,OAAO,EACN,KAAK,mBAAmB,EAExB,MAAM,8CAA8C,CAAA;AAKrD,KAAK,2BAA2B,GAC7B,sBAAsB,GACtB,kBAAkB,GAClB,CAAC,MAAM,GAAG,EAAE,CAAC,CAAA;AAEhB,KAAK,uBAAuB,GAAG,oBAAoB,CAAC,2BAA2B,CAAC,CAAA;AAEhF,MAAM,MAAM,kBAAkB,GAC3B;IACA,QAAQ,EAAE,mBAAmB,GAAG,IAAI,CAAA;IACpC,KAAK,CAAC,EAAE,SAAS,CAAA;CAChB,GACD;IACA,QAAQ,EAAE,IAAI,CAAA;IACd,KAAK,EAAE,uBAAuB,CAAA;CAC7B,CAAA;AAEJ;;;;;GAKG;AACH,wBAAsB,+BAA+B,CACpD,QAAQ,GAAE,MAAM,GAAG,SAEQ,GACzB,OAAO,CAAC,kBAAkB,CAAC,CAgE7B"}
+{"version":3,"file":"loadManifest.d.ts","sourceRoot":"","sources":["../../../../home/runner/work/custom-blocks/custom-blocks/sdk/src/bridge/loadManifest.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,4CAA4C,CAAA;AACtF,OAAO,EACN,KAAK,mBAAmB,EAExB,MAAM,8CAA8C,CAAA;AAKrD,KAAK,2BAA2B,GAC7B,sBAAsB,GACtB,kBAAkB,GAClB,CAAC,MAAM,GAAG,EAAE,CAAC,CAAA;AAEhB,KAAK,uBAAuB,GAAG,oBAAoB,CAAC,2BAA2B,CAAC,CAAA;AAEhF,MAAM,MAAM,kBAAkB,GAC3B;IACA,QAAQ,EAAE,mBAAmB,GAAG,IAAI,CAAA;IACpC,KAAK,CAAC,EAAE,SAAS,CAAA;CAChB,GACD;IACA,QAAQ,EAAE,IAAI,CAAA;IACd,KAAK,EAAE,uBAAuB,CAAA;CAC7B,CAAA;AAEJ;;;;;;GAMG;AACH,wBAAsB,+BAA+B,CACpD,QAAQ,GAAE,MAAM,GAAG,SAEQ,GACzB,OAAO,CAAC,kBAAkB,CAAC,CAgE7B"}

package/dist/bridge/loadManifest.js

@@ -1,9 +1,10 @@
 import { manifestSchema, } from "../protocol/manifest.js";
 import * as v from "valibot";
-const MANIFEST_URL = "/manifest";
+const MANIFEST_URL = "manifest";
 /**
  * On the literal `localhost` hostname, attempts to load the custom block's optional self-hosted
- * manifest exposed by the worker dev shell at `/manifest`.
+ * manifest exposed by the worker dev shell, requested at the page-relative `manifest` path so
+ * blocks served from a subpath resolve it against their own base.
  *
  * It is up to the host to decide whether to use this manifest or provide its own persisted manifest.
  */

package/dist/init.js

@@ -40,7 +40,8 @@ export function initCustomBlock(opts = {}) {
 }
 /**
  * Performs the host <-> sandbox SDK handshake:
- * 1. On localhost, attempts to load the worker manifest from `/manifest`
+ * 1. On localhost, attempts to load the worker manifest from the page-relative
+ *    `manifest` path
  * 2. Sends `connect` with the manifest
  * 3. Awaits the host's `init` message
  * 4. Applies the `init` payload and acknowledges with `initResult` (fire-and-forget)

package/dist/version.js

@@ -4,4 +4,4 @@
  *
  * WARNING: Generated during SDK publish. Do not edit in the published package.
  */
-export const CUSTOM_BLOCKS_SDK_VERSION = "0.1.28"
+export const CUSTOM_BLOCKS_SDK_VERSION = "0.1.29"

package/docs/deployment.md

@@ -11,7 +11,7 @@ A custom block manifest describes the data sources a block requires, including t
 
 Run `ntn customblocks dev` from a worker. It builds the worker, extracts its custom block declarations, starts one localhost Vite server per block, and renders them in the mock host at http://localhost:9873.
 
-At startup, the SDK fetches `/manifest` only when the bundle's hostname is exactly `localhost`, then forwards the response in `connect`. On every other hostname, the SDK skips this fetch and relies on the host-provided manifest from `init`.
+At startup, the SDK fetches the page-relative `manifest` path only when the bundle's hostname is exactly `localhost`, then forwards the response in `connect`. On every other hostname, the SDK skips this fetch and relies on the host-provided manifest from `init`.
 
 ## Types
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@notionhq/custom-blocks",
-	"version": "0.1.28",
+	"version": "0.1.29",
 	"license": "MIT",
 	"type": "module",
 	"publishConfig": {

package/src/bridge/loadManifest.ts

@@ -5,7 +5,7 @@ import {
 } from "@notionhq/custom-blocks-protocol/manifest.js"
 import * as v from "valibot"
 
-const MANIFEST_URL = "/manifest"
+const MANIFEST_URL = "manifest"
 
 type CustomBlockConnectErrorCode =
 	| "manifest_unavailable"
@@ -26,7 +26,8 @@ export type ManifestLoadResult =
 
 /**
  * On the literal `localhost` hostname, attempts to load the custom block's optional self-hosted
- * manifest exposed by the worker dev shell at `/manifest`.
+ * manifest exposed by the worker dev shell, requested at the page-relative `manifest` path so
+ * blocks served from a subpath resolve it against their own base.
  *
  * It is up to the host to decide whether to use this manifest or provide its own persisted manifest.
  */

package/src/init.ts

@@ -84,7 +84,8 @@ export function initCustomBlock(
 
 /**
  * Performs the host <-> sandbox SDK handshake:
- * 1. On localhost, attempts to load the worker manifest from `/manifest`
+ * 1. On localhost, attempts to load the worker manifest from the page-relative
+ *    `manifest` path
  * 2. Sends `connect` with the manifest
  * 3. Awaits the host's `init` message
  * 4. Applies the `init` payload and acknowledges with `initResult` (fire-and-forget)