paintcannon-react 0.0.45 → 0.0.47

package/README.md

@@ -147,8 +147,15 @@ All host components accept these event props:
 - `onTransitionEnd`
 - `onScroll`
 
-`onPaste` receives the same `PaintClipboardEvent` as core, including detected terminal image paths
-through `event.clipboardData.files`.
+`onPaste` receives the same `PaintClipboardEvent` as core, including image files through
+`event.clipboardData.files`. This also handles images copied from browsers or screenshot tools
+without a backing file on terminals supporting Kitty's rich-paste protocol. Image pastes have
+empty text data; no React-specific handling is needed.
+Use `await paintCannon.supportsRichPaste()` on the core instance to detect copied-image paste
+support before offering it in your UI.
+Inside tmux, core uses DCS passthrough only after confirming `focus-events` is on, so rich-paste
+mode can be released when switching away from the app's pane. Otherwise `supportsRichPaste()`
+returns `false`, leaving ordinary text and file-path paste available.
 
 `style` accepts the following CSS property names. Kebab-case and camelCase are
 both supported:
@@ -256,6 +263,38 @@ both supported:
 - `useAnimation()` for requestAnimationFrame-driven animations that share a
   single render cycle.
 
+## Desktop Notifications
+
+Use the core API through `useApp().paintCannon`; no notification-specific React
+wrapper is needed:
+
+```tsx
+function NotifyButton() {
+  const { paintCannon } = useApp();
+  return (
+    <Button
+      onClick={() => {
+        new paintCannon.Notification("Build complete", { body: "All tests passed." });
+      }}
+    >
+      Notify
+    </Button>
+  );
+}
+```
+
+`requestPermission()` automatically grants when a backend is available, or returns
+`"denied"` otherwise, without a prompt. Rust selects OSC 99/777/9 or a local macOS/Linux command fallback;
+it never invokes a remote desktop fallback over SSH. Notification lifecycle
+feedback varies by backend. See [the core notification API](../paintcannon/README.md#desktop-notifications)
+for options, events, replacement, and dismissal limitations.
+
+Use `await paintCannon.Notification.supportsClose()` to decide whether to render a
+dismiss button. Permission to deliver notifications does not imply dismissal
+support. OSC 99 features, including dismissal, are queried from the terminal at
+runtime. OSC 9/777 and the macOS command fallback cannot dismiss notifications
+programmatically; Otty's current acknowledgement also does not advertise dismissal.
+
 ## Core Runtime
 
 This package depends on `paintcannon`, which provides the NAPI-RS native

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "paintcannon-react",
-  "version": "0.0.45",
+  "version": "0.0.47",
   "license": "ISC",
   "repository": {
     "type": "git",
@@ -37,7 +37,7 @@
     "scheduler": "^0.25.0"
   },
   "peerDependencies": {
-    "paintcannon": "^0.0.45",
+    "paintcannon": "^0.0.47",
     "react": "^19.0.0"
   },
   "devDependencies": {