@urun-sh/next 0.2.55 → 0.2.56
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.
- package/README.md +14 -0
- package/dist/index.cjs +3 -3
- package/dist/index.d.cts +2 -1
- package/dist/index.js +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -112,6 +112,20 @@ The end state: a user sets only `URUN_API_KEY` and runs `urun deploy` — no
|
|
|
112
112
|
Canonical env vars (plain server env, not `NEXT_PUBLIC_*`): `URUN_GATEWAY_URL`
|
|
113
113
|
(default `https://api.urun.sh`), `URUN_APP`, `URUN_FUNCTION`.
|
|
114
114
|
|
|
115
|
+
## `urun dev` sessions
|
|
116
|
+
|
|
117
|
+
`urun dev` deploys your app to the segregated dev app `<your-app>--dev` while
|
|
118
|
+
your frontend keeps naming its base app. The token route makes the sessions it
|
|
119
|
+
mints for land there by declaring **dev mode** on the minted token — set from
|
|
120
|
+
the `URUN_DEV` server env var `urun dev` injects (`1` / `true`, case-insensitive;
|
|
121
|
+
anything else, including unset, is off), or explicitly with `createTokenRoute({ dev: true })`,
|
|
122
|
+
which wins over the env var.
|
|
123
|
+
|
|
124
|
+
The **platform** resolves `<app>--dev` from that declaration — nothing in the
|
|
125
|
+
SDK or your frontend ever suffixes an app name, so your app name stays the one
|
|
126
|
+
you wrote. The declaration is server-side only: a browser request body can
|
|
127
|
+
never set it.
|
|
128
|
+
|
|
115
129
|
## Server SDK
|
|
116
130
|
|
|
117
131
|
The underlying mint call is `createClientToken(apiKey, options)` from
|