@notionhq/custom-blocks 0.1.12 → 0.1.14

package/README.md

@@ -104,7 +104,6 @@ API surface, one page per category. Import framework-neutral APIs from `@notionh
 - [`docs/users.md`](./docs/users.md) — `users.list / get`, the `NotionUser` shape, paging.
 - [`docs/errors.md`](./docs/errors.md) — request results, error format, error codes, retries, and initialization failures.
 - [`docs/deployment.md`](./docs/deployment.md) — worker-backed deploys, localhost self-hosted fallback, where the manifest comes from.
-- [`docs/vite-plugin.md`](./docs/vite-plugin.md) — the `notionCustomBlock()` Vite plugin.
 
 ## Forbidden APIs
 

package/dist/protocol/messages/init.js

@@ -36,7 +36,7 @@ export const initMessageSchema = v.variant("status", [
         initializationId: v.string(),
         status: v.literal("success"),
         theme: notionThemeSchema,
-        // TODO(custom-blocks): Make this required when next bumping the protocol version.
+        // TODO(custom-blocks): Make this required when bumping bridge protocol version 4.
         contrastMode: v.optional(notionContrastModeSchema, DEFAULT_CONTRAST_MODE),
         blockId: notionBlockIdSchema,
         parent: notionParentSchema,

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.12"
+export const CUSTOM_BLOCKS_SDK_VERSION = "0.1.14"

package/package.json

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

package/vite-plugin/index.d.ts

@@ -1,17 +1,12 @@
-/**
- * Type declarations for the Vite plugin. The runtime lives in `vite.js` —
- * see that file for behavior, options, and the reasoning for splitting `.js`
- * + `.d.ts` instead of using a single `.ts` source.
- */
-
-type UserConfig = { base?: string }
-
 export type NotionCustomBlockPlugin = {
 	name: string
-	config: (userConfig: UserConfig) => { base: string }
 }
 
 /**
- * Vite plugin that configures relative asset paths for custom block bundles.
+ * Vite plugin for Notion custom blocks.
+ *
+ * @deprecated This compatibility stub does nothing. Remove it from Vite config when possible.
+ *
+ * TODO(custom-blocks): Remove this when bumping bridge SDK version to 0.2.0.
  */
 export function notionCustomBlock(): NotionCustomBlockPlugin

package/vite-plugin/index.js

@@ -1,46 +1,11 @@
 /**
- * Vite plugin half of `@notionhq/custom-blocks`.
+ * Vite plugin for Notion custom blocks.
  *
- * Authored as plain JS (with `index.d.ts` co-located for types) — the rest of
- * the SDK is `.ts` consumed directly via the workspace symlink, but Vite's
- * config loader resolves this subpath through Node's ESM resolver, which
- * can't load `.ts` source files. Lives in its own `vite-plugin/` directory
- * so it can grow its own tsconfig later.
+ * @deprecated This is just a compatibility stub to ensure existing block code can continue to work
+ * with the new SDK.
  *
- * Usage:
- *
- *   import { notionCustomBlock } from "@notionhq/custom-blocks/vite"
- *
- *   export default defineConfig({
- *     plugins: [react(), notionCustomBlock()],
- *   })
- *
- * Requires `"type": "module"` in the consuming project's `package.json` so
- * Vite's config loader uses Node's ESM resolver (not CommonJS `require`,
- * which fails for ESM-only deps).
- *
- * The worker dev shell owns the localhost `/manifest` route. This plugin only
- * controls bundle asset paths.
+ * TODO(custom-blocks): Remove this when bumping bridge SDK version to 0.2.0.
  */
-const REQUIRED_BASE = "./"
-
 export function notionCustomBlock() {
-	return {
-		name: "custom-blocks:bundle-base",
-		config(userConfig) {
-			// Custom blocks are served from a content-addressed path that
-			// has trailing slashes, eg https://dev.notion.so/custom-block-bundle/357b35e6-e67f-81fd-b425-00e7b3e2afd1/
-			// so all asset URLs in the built bundle must be relative.
-			// Force `base: "./"` and reject any other explicit value
-			//
-			// Note: once we are set up with a wildcard subdomain host, this will no longer be necessary
-			// and should be removed, since /assets will work fine.
-			if (userConfig.base !== undefined && userConfig.base !== REQUIRED_BASE) {
-				throw new Error(
-					`@notionhq/custom-blocks/vite: \`base\` must be "${REQUIRED_BASE}" (got ${JSON.stringify(userConfig.base)}). Custom blocks need relative asset paths so the bundle works under any host-served prefix.`,
-				)
-			}
-			return { base: REQUIRED_BASE }
-		},
-	}
+	return { name: "custom-blocks:legacy-vite-plugin" }
 }

package/docs/vite-plugin.md

@@ -1,17 +0,0 @@
-# Vite plugin
-
-The `notionCustomBlock()` plugin from `@notionhq/custom-blocks/vite` configures a block's build output for Notion hosting.
-
-```ts
-import { defineConfig } from "vite";
-import react from "@vitejs/plugin-react";
-import { notionCustomBlock } from "@notionhq/custom-blocks/vite";
-
-export default defineConfig({
-  plugins: [react(), notionCustomBlock()],
-});
-```
-
-It forces `base: "./"` and rejects any other explicit value. Custom blocks are served from a content-addressed path, so asset URLs in the built bundle must be relative.
-
-The plugin does not serve or emit manifests. Declare the manifest with `worker.customBlock(...)`; the worker dev shell exposes it dynamically at `/manifest` during local development. See [deployment.md](./deployment.md) for more information.