SDKs the way they should be
Typed, framework-agnostic, versioned on a CDN. The widget is the first; future SDKs land as listings.
Every integration surface Reqdesk exposes is documented, typed, and versioned. The widget was the first; the catalogue grows from there. Browser extensions, server-side SDKs, framework-specific helpers, and themes all land in the same /extensions index.
What is in the catalogue today
@reqdesk/widget— the embeddable bilingual support widget.
What is on the way
@reqdesk/sdk-core— typed JavaScript client for the public API.@reqdesk/sdk-react— React hooks and components for embedding the customer portal in an existing app.- A Filament plugin — for Laravel teams who want a Reqdesk dashboard inside their existing back-office.
How a new entry joins the catalogue
The catalogue is file-based: each extension is an MDX entry in this site’s src/content/extensions/ collection. Adding a new entry is a pull request — there is no proprietary CMS to learn, and the listing renders the same way the widget’s does.
Versioning
Anything published to cdn.reqdesk.support carries an immutable version path: /<package>/<version>/.... The CDN never silently drops a version that consumers are pinned to. The retention list is in the open at docker/reqdesk-cdn/retained-versions.txt.