nocobase-app-plugin-notification-in-app

Registers, verifies, and diagnoses the NocoBase durable in-app notification inbox plugin.

9|3|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/nocobase/nocobase3 --skill nocobase-app-plugin-notification-in-app-nocobase
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nocobase-app-plugin-notification-in-app
Source: https://github.com/nocobase/nocobase3/tree/main/packages/plugins/app-plugin-notification-in-app/skills/nocobase-app-plugin-notification-in-app
Command: npx skills add https://github.com/nocobase/nocobase3 --skill nocobase-app-plugin-notification-in-app-nocobase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Integrating the NocoBase in-app notification inbox requires correctly registering Client and Server plugin entries, wiring authenticated HTTP and realtime clients, and keeping durable inbox state authoritative—mistakes here cause broken isolation, failed CSRF mutations, or stale unread counts. ## Core Features & Use Cases - Plugin Registration: Registers the core notification Server plugin and the in-app Client/Server entries in a target NocoBase application. - Verification & Diagnosis: Checks inbox HTTP access, CSRF-protected mutations, per-user isolation, realtime invalidation, and reconnect refresh behavior. - Use Case: An agent adds the in-app inbox to a NocoBase application, opens the development-only page at /dev/notification-in-app, and confirms that a valid inbox.changed realtime event triggers a bounded HTTP refetch without exposing the Dev Route in production builds. ## Quick Start Ask the agent to register and verify the in-app notification inbox plugin for your NocoBase application, specifying the target application and whether to register, verify, or diagnose.

Frequently Asked Questions about nocobase-app-plugin-notification-in-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register the NocoBase in-app notification plugin in an application?▼

Register @nocobase/app-plugin-notification/server before @nocobase/app-plugin-notification-in-app/server when the in-app Channel is needed, then register the package's /client entry in the Client composition root. Always import the public /client and /server entries, never internal implementation files.

How do I verify the in-app inbox page during development?▼

Open the development-only route at /dev/notification-in-app relative to the App base path after registering the Client plugin. The Dev Route and its page module are excluded from production builds, and its Provider mounts only while the page is open.

Does the in-app inbox support a custom API base URL?▼

Yes, inbox HTTP and WebSocket traffic use the injected ApiClient and RealtimeClient configured with the application's api.baseURL and api.realtimeURL. Never derive endpoints from window.location, a Portal base, or the WebSocket URL.

Why is my inbox UI not updating when a realtime event arrives?▼

Realtime events are only invalidation signals, not authoritative state. Confirm the subscription uses the public topic constant, that a valid inbox.changed event triggers an HTTP refetch, and that connection reopen and window focus also refetch durable state.

Can realtime event payloads be rendered as inbox content?▼

No, realtime payloads must never be rendered as authoritative inbox content. Durable HTTP state remains the source of truth, and malformed or unrelated payloads must be ignored without altering displayed state.