onlyoffice/onlyoffice-devtools

Embed ONLYOFFICE Apps (formerly DocSpace) into web apps with the Embed SDK (@onlyoffice/docspace-sdk-js). Use when the user wants to embed an ONLYOFFICE Apps file manager, document editor or viewer, room/file selector dialog, file uploader, forms gallery, AI chat, or personal files section; when configuring TFrameConfig, authentication (login hash flow, OAuth getToken, public room tokens, API keys, 2FA questions), frame events, SDKInstance methods, or programmatic form filling via executeInEditor; when a host app (WordPress, Nextcloud, CRM, React/Next/Vue/Angular page) shows a DocSpace iframe that is blank, returns 401, fails CSP or X-Frame-Options; or when a connector built on this SDK needs a new login or file flow. Not for DocSpace plugins (apps-plugin-sdk) or for the Document Server Docs API outside an embedded frame.

Build, audit and explain ONLYOFFICE Apps (formerly DocSpace) plugins made with the Plugins SDK. Use whenever someone wants to create, scaffold, extend or change one, or describes a feature inside the portal without naming the SDK, React or the UI kit — an item in the context menu, main button or profile menu, a page in the sidebar, a tab in the info panel, a handler for a custom file type, a reaction to a portal event, an admin settings form ("a button in ONLYOFFICE Apps that converts a file", "a screen inside ONLYOFFICE Apps listing our rooms"). Use it too when a plugin installs but does nothing, renders blank, shows for the wrong users or does not change after a re-upload; when someone asks to review, debug, fix or migrate an existing plugin; and for questions about scopes, hooks, items, actions or how the portal loads plugins. Not for document-editor plugins (ONLYOFFICE Docs plugins and macros), for embedding ONLYOFFICE Apps into another site (apps-embed-sdk), or for standalone REST API scripts.

Build React 19 screens with the ONLYOFFICE UI kit (@onlyoffice/apps-ui-kit) in your own web app — forms, dialogs, side panels, lists, empty states, toasts, theming and translations. Use when someone wants their app to look like ONLYOFFICE DocSpace or Apps ("a dialog in the DocSpace style", "a settings form like the portal's", "use the DocSpace components in our admin") even if they never name the kit; when they ask which kit component fits a job or what a prop is called (visible vs isVisible vs isOpen vs open); when kit components render unstyled, with empty labels, an i18n console error, a collapsed toggle, a 1px textarea or doubled spacing; when an import from the kit does not resolve or pulls in portal-only modules (selectors, billing, uploader); or when reviewing code that uses the kit. Not for plugins inside the DocSpace portal (apps-plugin-sdk), for embedding DocSpace in an iframe (apps-embed-sdk), or for other component libraries.