@authup/client-auth-console 1.0.0-beta.65 → 1.0.0-beta.66
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 +3 -2
- package/dist/client/.vite/ssr-manifest.json +1950 -654
- package/dist/client/assets/index-CR-eHMTZ.js +97 -0
- package/dist/client/index.html +1 -1
- package/dist/server/server.js +2611 -839
- package/package.json +14 -14
- package/src/contract.ts +13 -1
- package/dist/client/assets/index-CyryR3Go.js +0 -92
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@authup/client-auth-console",
|
|
3
|
-
"version": "1.0.0-beta.
|
|
3
|
+
"version": "1.0.0-beta.66",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"license": "AGPL-3.0-only",
|
|
6
6
|
"description": "Authup's auth console: the SSR auth workflow UI (authorize, register, activate, password recovery, logout) rendered by server-core on the IdP origin.",
|
|
@@ -25,28 +25,28 @@
|
|
|
25
25
|
"node": "^22.13.0 || ^23.5.0 || >=24.0.0"
|
|
26
26
|
},
|
|
27
27
|
"dependencies": {
|
|
28
|
-
"@authup/core-http-kit": "^1.0.0-beta.
|
|
28
|
+
"@authup/core-http-kit": "^1.0.0-beta.66"
|
|
29
29
|
},
|
|
30
30
|
"devDependencies": {
|
|
31
|
-
"@authup/client-web-kit": "^1.0.0-beta.
|
|
32
|
-
"@authup/client-web-kit-theme": "^1.0.0-beta.
|
|
33
|
-
"@authup/client-web-theme": "^1.0.0-beta.
|
|
34
|
-
"@authup/core-kit": "^1.0.0-beta.
|
|
35
|
-
"@authup/i18n": "^1.0.0-beta.
|
|
36
|
-
"@authup/kit": "^1.0.0-beta.
|
|
31
|
+
"@authup/client-web-kit": "^1.0.0-beta.66",
|
|
32
|
+
"@authup/client-web-kit-theme": "^1.0.0-beta.66",
|
|
33
|
+
"@authup/client-web-theme": "^1.0.0-beta.66",
|
|
34
|
+
"@authup/core-kit": "^1.0.0-beta.66",
|
|
35
|
+
"@authup/i18n": "^1.0.0-beta.66",
|
|
36
|
+
"@authup/kit": "^1.0.0-beta.66",
|
|
37
37
|
"@fontsource/asap": "^5.3.0",
|
|
38
38
|
"@fontsource/nunito": "^5.3.0",
|
|
39
39
|
"@iconify-json/fa6-brands": "^1.2.0",
|
|
40
40
|
"@iconify-json/fa6-solid": "^1.2.0",
|
|
41
|
-
"@iconify/vue": "^5.0.
|
|
41
|
+
"@iconify/vue": "^5.0.2",
|
|
42
42
|
"@ilingo/validup": "^1.2.0",
|
|
43
43
|
"@ilingo/validup-vue": "^1.2.0",
|
|
44
44
|
"@ilingo/vue": "^6.1.0",
|
|
45
45
|
"@nuxt/icon": "^2.5.1",
|
|
46
46
|
"@tailwindcss/vite": "^4.3.3",
|
|
47
47
|
"@validup/vue": "^2.0.1",
|
|
48
|
-
"@vitejs/plugin-vue": "^6.0.
|
|
49
|
-
"@vue/test-utils": "^2.5.
|
|
48
|
+
"@vitejs/plugin-vue": "^6.0.9",
|
|
49
|
+
"@vue/test-utils": "^2.5.1",
|
|
50
50
|
"@vuecs/button": "^1.4.1",
|
|
51
51
|
"@vuecs/core": "^3.5.0",
|
|
52
52
|
"@vuecs/countdown": "^2.1.0",
|
|
@@ -66,12 +66,12 @@
|
|
|
66
66
|
"@vuecs/theme-tailwind": "^6.4.2",
|
|
67
67
|
"@vuecs/timeago": "^2.2.0",
|
|
68
68
|
"cross-env": "^10.1.0",
|
|
69
|
-
"happy-dom": "^20.14.
|
|
69
|
+
"happy-dom": "^20.14.5",
|
|
70
70
|
"pinia": "^4.0.3",
|
|
71
71
|
"tailwindcss": "^4.3.1",
|
|
72
|
-
"vite": "^8.
|
|
72
|
+
"vite": "^8.3.0",
|
|
73
73
|
"vitest": "^4.0.14",
|
|
74
|
-
"vue": "^3.5.
|
|
74
|
+
"vue": "^3.5.43",
|
|
75
75
|
"vue-router": "^5.3.1",
|
|
76
76
|
"vue-tsc": "^3.3.11"
|
|
77
77
|
},
|
package/src/contract.ts
CHANGED
|
@@ -29,11 +29,23 @@ import type { IClient } from '@authup/core-http-kit';
|
|
|
29
29
|
* against an older contract would otherwise fail per request on
|
|
30
30
|
* `/authorize` rather than at boot with an actionable message.
|
|
31
31
|
*/
|
|
32
|
-
export const CONTRACT_VERSION =
|
|
32
|
+
export const CONTRACT_VERSION = 5;
|
|
33
33
|
|
|
34
34
|
/*
|
|
35
35
|
* History:
|
|
36
36
|
*
|
|
37
|
+
* 5 - the `/device` payload carries `federatedLogin: { providerId }` and the
|
|
38
|
+
* page has to complete it the way `/authorize` does (version 3), then
|
|
39
|
+
* return to the code step (#3589). The provider buttons live in the kit,
|
|
40
|
+
* so a package built on the new kit whose own page ignores the field
|
|
41
|
+
* sends the person code, login, provider and back to the code in a loop,
|
|
42
|
+
* with the provider's code spent each time.
|
|
43
|
+
*
|
|
44
|
+
* 4 - the host renders `/device` (the RFC 8628 device verification page,
|
|
45
|
+
* plan 065) with a payload of `{ features, userCode? }`; a bundle built
|
|
46
|
+
* against 3 answers an empty `<div id="app">` for every device
|
|
47
|
+
* verification with no error anywhere, the version-2 precedent.
|
|
48
|
+
*
|
|
37
49
|
* 3 - the `/authorize` payload carries `federatedLogin: { providerId }` and
|
|
38
50
|
* the page has to complete it with a payload-less, same-origin
|
|
39
51
|
* `POST /identity-providers/:id/login-complete`. The pending login rides
|