@dogeos/dogeos-sdk 4.0.0-beta.8 → 4.0.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 +8 -11
- package/dist/dogeos-sdk.css +1 -1
- package/dist/index.d.ts +14 -0
- package/dist/index.js +14212 -13939
- package/package.json +6 -6
package/README.md
CHANGED
|
@@ -17,13 +17,9 @@ The npm package is built with deployment-owned public service destinations. The
|
|
|
17
17
|
- `DOGEOS_EMBEDDED_WALLET_STAGE`
|
|
18
18
|
- `DOGEOS_SDK_AUTH_SERVICE_ORIGINS` (comma-separated gateway/service origins)
|
|
19
19
|
|
|
20
|
-
The build fails when any required value is missing or invalid. These values are compiled into the published SDK and are not consumer provider options.
|
|
20
|
+
The build fails when any required value is missing or invalid. These values are compiled into the published SDK and are not consumer provider options.
|
|
21
21
|
|
|
22
|
-
The SDK directory is a library-only package.
|
|
23
|
-
its Vite entrypoint and application tests live in
|
|
24
|
-
[`apps/sdk-demo`](../../apps/sdk-demo/README.md). Use `pnpm watch:demo` from the
|
|
25
|
-
repository root for the supported SDK-and-app development loop; the app still
|
|
26
|
-
resolves this package through its public `dist` export.
|
|
22
|
+
The SDK directory is a library-only package. Consumers resolve it through its public `dist` export.
|
|
27
23
|
|
|
28
24
|
## Installation
|
|
29
25
|
|
|
@@ -299,11 +295,12 @@ export function App() {
|
|
|
299
295
|
}
|
|
300
296
|
```
|
|
301
297
|
|
|
302
|
-
Provider credentials
|
|
303
|
-
|
|
304
|
-
controls and provide their registered DogeOS client ID. A successful SDK
|
|
305
|
-
continues to the associated embedded wallet automatically; returning
|
|
306
|
-
connections are restored by the provider without consumer session
|
|
298
|
+
Provider OAuth client IDs and credentials are owned by the DogeOS authentication
|
|
299
|
+
authority for each environment. Consumer applications select the enabled login
|
|
300
|
+
controls and provide only their registered DogeOS client ID. A successful SDK
|
|
301
|
+
login continues to the associated embedded wallet automatically; returning
|
|
302
|
+
wallet connections are restored by the provider without consumer session
|
|
303
|
+
plumbing.
|
|
307
304
|
|
|
308
305
|
### Configure Theme
|
|
309
306
|
|