SDK examples index
Runnable and copy-paste examples for every official SDK, plus the multi-app cluster demo.
Packages
| SDK | Package | Package examples | Quickstart |
|---|---|---|---|
| Node.js | @mpratyush54/sdk-node |
sdk-node/examples |
Node quickstart |
| React | @mpratyush54/sdk-react |
sdk-react/examples |
React quickstart |
| Angular | @mpratyush54/sdk-angular |
sdk-angular/examples |
Angular quickstart |
| Python | mpratyush54-sdk |
sdk-python/examples |
Python quickstart |
Cluster demo (Node + React + Angular)
examples/sdk-apps registers via the Node SDK, ensures Postgres/Mongo/Redis, serves React and Angular UIs, and ships telemetry to the portal.
cd examples/sdk-apps
$env:PLATFORM_SDK_TOKEN='sdk_live_...'
./start-demos.ps1
Common prerequisites
- Create a project in the portal.
- Create an SDK token (Project → SDK Tokens). Pick the kind by where it runs:
- Server for backend SDKs (Node, Python): reads project config/secrets, registers services.
- Browser for frontend SDKs (React, Angular): only sends bug reports, logs and API metrics. Frontend config is public, so never ship a server token to a browser. If an SDK token was previously embedded in a frontend, revoke it and create new tokens of the right kind.
- Set
PLATFORM_URL/PLATFORM_SDK_TOKEN(and project id where required). - For GitOps demos, set the project repository URL to the same git remote the SDK sends.
Publishing
CI publishes SDKs using npm Trusted Publishers + PyPI OIDC. See the SDK publishing workflow for the publishing configuration.