@lessly/sdk-app 32.1.0 → 32.1.1

package/docs/recipes/local-dev.md

@@ -23,6 +23,10 @@ forwarded through a bearer proxy at exactly this path:
 proxies through `/lessly-api`, so your SDK client just talks to that path in
 dev — it never sees or handles the token itself.
 
+So in dev you pass `baseUrl: '/lessly-api'` — a page-relative `baseUrl` is
+supported and resolved against the current document (browser-only); see
+`recipes/sdk-usage.md`.
+
 ### Device-code login
 
 The first time you run `pnpm dev` (or once your local session expires),

package/docs/recipes/sdk-usage.md

@@ -26,6 +26,26 @@ await sdk.organization.product.create({ name: 'Acme' });
 > [Namespaces and subpath imports](#namespaces-and-subpath-imports). The calls
 > above use `organization`; substitute the namespace/resource you need.
 
+### `baseUrl`: absolute or page-relative
+
+`baseUrl` may be either form:
+
+- **Absolute** — `'https://api.lessly.dev'`. Works anywhere, including SSR and
+  tests.
+- **Page-relative** — `'/lessly-api'`, the path `pnpm dev` proxies through
+  (see `recipes/local-dev.md`). It is resolved against the current document via
+  `globalThis.location`, so it is **browser-only**: outside a browser the SDK
+  throws a named error (`@lessly/sdk-app: relative baseUrl "/lessly-api" cannot
+  be resolved outside a browser`) instead of an opaque `Invalid URL`. Tests and
+  SSR must pass an absolute base.
+
+```ts
+const sdk = createLesslyApp({
+  baseUrl: import.meta.env.DEV ? '/lessly-api' : 'https://api.lessly.dev',
+  productId: 'prod_123',
+});
+```
+
 `productId` is the active product — read it from your `./App` props or the
 `X-Product-Id` header (see APP-005), never decoded from a token.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lessly/sdk-app",
-  "version": "32.1.0",
+  "version": "32.1.1",
   "type": "module",
   "sideEffects": false,
   "engines": {