@zitadel/sdk-react 0.1.0-alpha.18 → 0.1.0-alpha.19

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +14 -12
  2. package/package.json +4 -4
package/README.md CHANGED
@@ -31,17 +31,19 @@ export function ProfilePage() {
31
31
  }
32
32
  ```
33
33
 
34
+ The signed-in session card is `<ZitadelSession project={project} />` (exported
35
+ as `ZitadelSession`).
36
+
34
37
  ## Proxying to the backend (deployment)
35
38
 
36
- The widgets call `${proxyPath}/…` same-origin (default `/__nextgen`). A SPA has no
37
- server, so in production the path comes from your hosting platform — a
38
- `vercel.json` rewrite, a `netlify.toml` redirect, or a minimal Cloudflare
39
- worker — with no secrets on the platform, per
40
- [ADR 036](https://github.com/zitadel/nextgen/blob/main/docs/adrs/036-api-credential-planes.md).
41
- CLI scaffolding for these configs is tracked in
42
- [zitadel/nextgen#560](https://github.com/zitadel/nextgen/issues/560). **Until
43
- that work lands, production SPA deployment is not yet supported** — the CLI dev
44
- proxy covers local development.
45
-
46
- For local development you can skip the proxy entirely and point `proxyPath` straight
47
- at the backend (cross-origin), e.g. `proxyPath: "http://localhost:4000"`.
39
+ The widgets call `${proxyPath}/…` same-origin (default `/__nextgen`). In
40
+ production the same-origin path must come from your hosting platform — until
41
+ the CLI can scaffold those configs, **production SPA deployment is not yet
42
+ supported**; see
43
+ [ADR 036](https://github.com/zitadel/nextgen/blob/main/docs/adrs/036-api-credential-planes.md)
44
+ and [zitadel/nextgen#560](https://github.com/zitadel/nextgen/issues/560). The
45
+ CLI dev proxy covers local development.
46
+
47
+ For local development you can also skip the proxy and point `proxyPath`
48
+ straight at the backend (cross-origin), e.g. `proxyPath: "http://localhost:8080"`
49
+ (the `zitadel start` local runtime default port).
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zitadel/sdk-react",
3
- "version": "0.1.0-alpha.18",
3
+ "version": "0.1.0-alpha.19",
4
4
  "description": "React components for the Zitadel auth UI (client-side SPA).",
5
5
  "homepage": "https://github.com/zitadel/nextgen/tree/main/packages/sdk-react#readme",
6
6
  "bugs": {
@@ -27,9 +27,9 @@
27
27
  },
28
28
  "dependencies": {
29
29
  "@lit/react": "^1.0.8",
30
- "@zitadel/api": "0.1.0-alpha.18",
31
- "@zitadel/sdk-core": "0.1.0-alpha.18",
32
- "@zitadel/components": "0.1.0-alpha.18"
30
+ "@zitadel/components": "0.1.0-alpha.19",
31
+ "@zitadel/sdk-core": "0.1.0-alpha.19",
32
+ "@zitadel/api": "0.1.0-alpha.19"
33
33
  },
34
34
  "peerDependencies": {
35
35
  "react": ">=18",