@atproto/oauth-client-browser 0.3.0 → 0.3.2
Sign up to get free protection for your applications and to get access to all the features.
- package/README.md +1 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -185,7 +185,7 @@ result of an authorization redirect (both `session` and `state` are defined).
|
|
|
185
185
|
|
|
186
186
|
### Initiating an OAuth flow
|
|
187
187
|
|
|
188
|
-
In order to initiate an OAuth flow, we must
|
|
188
|
+
In order to initiate an OAuth flow, we must first determine which PDS the
|
|
189
189
|
authentication flow will be initiated from. This means that the user must
|
|
190
190
|
provide one of the following information:
|
|
191
191
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@atproto/oauth-client-browser",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.2",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"description": "ATPROTO OAuth client for the browser (relies on WebCrypto & Indexed DB)",
|
|
6
6
|
"keywords": [
|
|
@@ -37,8 +37,8 @@
|
|
|
37
37
|
"@atproto/did": "0.1.3",
|
|
38
38
|
"@atproto/jwk": "0.1.1",
|
|
39
39
|
"@atproto/jwk-webcrypto": "0.1.2",
|
|
40
|
-
"@atproto/oauth-client": "0.3.
|
|
41
|
-
"@atproto/oauth-types": "0.2.
|
|
40
|
+
"@atproto/oauth-client": "0.3.2",
|
|
41
|
+
"@atproto/oauth-types": "0.2.1"
|
|
42
42
|
},
|
|
43
43
|
"devDependencies": {
|
|
44
44
|
"typescript": "^5.6.3"
|