Platform SDK
One package — @synopackageland/dev-sdk — with runtime-safe imports for browser, server, and Node clients. No extra adapter packages.
Intended install: npm i @synopackageland/dev-sdk. Public npm may not be published yet.
Entry points
| Import | Use when |
|---|---|
@synopackageland/dev-sdk/browser | Web UI in the browser — requireLogin, User Context, File API. |
@synopackageland/dev-sdk/server | HTTP handlers inside the App container. |
@synopackageland/dev-sdk/node | Headless Client, workers, and CLI tools representing an App User. |
When you need it
Apps without DSM identity or File API can skip the SDK at runtime and still use Developer Kit to generate a Docker-based SPK. Integrated Apps that need platform capabilities install one SDK package and declare integration in App Contract.
Identity declaration
Publishers declare integration.identity.mode: broker-managed. Developer Kit generates callback paths, Package launcher, Trusted App Entry, and runtime bootstrap. v1 default does not ask for NAS domain, OIDC issuer, or full redirect URI fields — zero-configuration entry uses the DSM URL the user already has open.
Framework examples (Express, Better Auth, and others) show how to verify User Context with the same verifier — they are samples, not separate published plugins.
Developer Kit vs Platform SDK
| Product | When | Role |
|---|---|---|
Developer Kit (synopkgland) | Build, validate, deploy, publish | Schema, CLI, analyzer, SPK generator, repository publisher |
| Platform SDK | App runtime on NAS | User Context, File API, shared errors |
| Skill Pack | Agent-driven authoring | Progressive skills; authority remains schema and tests |