@ulabase/kit-ng 0.12.0 → 0.13.0
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 +5 -5
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Wraps [`@ulabase/kit`](https://www.npmjs.com/package/@ulabase/kit) in Angular services with signals, route guards, and an HTTP interceptor — authentication in `RhAuthService`, and [payments](#rhpaymentsservice) in `RhPaymentsService`.
|
|
4
4
|
|
|
5
|
-
Pairs with [Ulabase](https://
|
|
5
|
+
Pairs with [Ulabase](https://ulabase.com), which gives you a production-ready backend — MongoDB, REST API, authentication, signup/signin, all managed.
|
|
6
6
|
|
|
7
7
|
## Installation
|
|
8
8
|
|
|
@@ -35,7 +35,7 @@ The kit supports **two authentication modes**:
|
|
|
35
35
|
- **Bearer token** (default) — stored in `localStorage`, sent as `Authorization: Bearer <token>`
|
|
36
36
|
- **Cookie** — JWT managed by the backend as an HttpOnly cookie, **same-origin only**
|
|
37
37
|
|
|
38
|
-
Pass `mode: 'cookie'` to `login()`, `activate()`, `resetPassword()`, or `switchTeam()` only when the app is served from the same origin as the service. Since a Ulabase service lives on `*.
|
|
38
|
+
Pass `mode: 'cookie'` to `login()`, `activate()`, `resetPassword()`, or `switchTeam()` only when the app is served from the same origin as the service. Since a Ulabase service lives on `*.ulabase.app` while your app lives on your own domain, that cookie is third-party and is blocked by default in Safari and Firefox — regardless of the server's CORS configuration. **Cross-origin apps, which is the normal case, should stay on the default `'bearer'` mode.**
|
|
39
39
|
|
|
40
40
|
Each of these calls a matching auto-login endpoint with `delivery=body` (bearer) or `delivery=cookie`, and in bearer mode gets the fresh token back in the same response — no extra login round-trip.
|
|
41
41
|
|
|
@@ -167,7 +167,7 @@ Payments live in their own service, because a subscription is not a session. It
|
|
|
167
167
|
|
|
168
168
|
```typescript
|
|
169
169
|
provideRhAuth({
|
|
170
|
-
apiBaseUrl: 'https://my-service.
|
|
170
|
+
apiBaseUrl: 'https://my-service.ulabase.app',
|
|
171
171
|
payments: true,
|
|
172
172
|
ownershipRole: 'owner', // default; set it if your deployment overrides the role
|
|
173
173
|
})
|
|
@@ -230,8 +230,8 @@ full reasoning.
|
|
|
230
230
|
|
|
231
231
|
The fastest path to a working app:
|
|
232
232
|
|
|
233
|
-
1. Create a service on [Ulabase](https://
|
|
234
|
-
2. Fork [`
|
|
233
|
+
1. Create a service on [Ulabase](https://ulabase.com)
|
|
234
|
+
2. Fork [`ulabase/starter-ng`](https://github.com/ulabase/starter-ng)
|
|
235
235
|
3. Set `apiBaseUrl` in `environment.ts`
|
|
236
236
|
4. `ng serve`
|
|
237
237
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@ulabase/kit-ng",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.13.0",
|
|
4
4
|
"description": "Angular services, route guards, and HTTP interceptor for Ulabase authentication and payments — wraps @ulabase/kit.",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -15,7 +15,7 @@
|
|
|
15
15
|
"rxjs": ">=7"
|
|
16
16
|
},
|
|
17
17
|
"dependencies": {
|
|
18
|
-
"@ulabase/kit": "0.
|
|
18
|
+
"@ulabase/kit": "0.13.0",
|
|
19
19
|
"tslib": "^2.3.0"
|
|
20
20
|
},
|
|
21
21
|
"module": "fesm2022/ulabase-kit-ng.mjs",
|