@cedarjs/auth-supabase-web 2.5.0 → 2.5.1-next.27
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 +4 -4
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -30,7 +30,7 @@ SUPABASE_KEY="..."
|
|
|
30
30
|
SUPABASE_JWT_SECRET="..."
|
|
31
31
|
```
|
|
32
32
|
|
|
33
|
-
Lastly, in your configuration file (`cedar.toml`
|
|
33
|
+
Lastly, in your configuration file (`cedar.toml`), include `SUPABASE_URL` and `SUPABASE_KEY` in the list of env vars that should be available to the web side:
|
|
34
34
|
|
|
35
35
|
```toml title="cedar.toml"
|
|
36
36
|
[web]
|
|
@@ -84,7 +84,7 @@ const HomePage = () => {
|
|
|
84
84
|
|
|
85
85
|
You will notice that [Supabase Javascript SDK Auth API](https://supabase.com/docs/reference/javascript/auth-api) reference documentation presents methods to sign in with the various integrations Supabase supports: password, OAuth, IDToken, SSO, etc.
|
|
86
86
|
|
|
87
|
-
The
|
|
87
|
+
The CedarJS implementation of Supabase authentication supports these as well, but within the `logIn` method of the `useAuth` hook.
|
|
88
88
|
|
|
89
89
|
That means that you will see that Supabase documents sign in with email password as:
|
|
90
90
|
|
|
@@ -95,7 +95,7 @@ const { data, error } = await supabase.auth.signInWithPassword({
|
|
|
95
95
|
})
|
|
96
96
|
```
|
|
97
97
|
|
|
98
|
-
In
|
|
98
|
+
In CedarJS, you will always use `logIn` and pass the necessary credential options and also an `authenticationMethod` to declare how you want to authenticate.
|
|
99
99
|
|
|
100
100
|
```ts
|
|
101
101
|
const { logIn } = useAuth()
|
|
@@ -276,7 +276,7 @@ Log in a user given a User supplied OTP received via mobile.
|
|
|
276
276
|
|
|
277
277
|
- The verification type used should be determined based on the corresponding auth method called before verifyOtp to sign up / sign-in a user.
|
|
278
278
|
|
|
279
|
-
The
|
|
279
|
+
The CedarJS auth provider doesn't expose the `veriftyOtp` method from the Supabase SDK directly.
|
|
280
280
|
|
|
281
281
|
Instead, since you always have access the the Supabase Auth client, you can access any method it exposes.
|
|
282
282
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cedarjs/auth-supabase-web",
|
|
3
|
-
"version": "2.5.
|
|
3
|
+
"version": "2.5.1-next.27+4a00a5632",
|
|
4
4
|
"repository": {
|
|
5
5
|
"type": "git",
|
|
6
6
|
"url": "git+https://github.com/cedarjs/cedar.git",
|
|
@@ -49,10 +49,10 @@
|
|
|
49
49
|
"test:watch": "vitest watch"
|
|
50
50
|
},
|
|
51
51
|
"dependencies": {
|
|
52
|
-
"@cedarjs/auth": "2.5.
|
|
52
|
+
"@cedarjs/auth": "2.5.1-next.27+4a00a5632"
|
|
53
53
|
},
|
|
54
54
|
"devDependencies": {
|
|
55
|
-
"@cedarjs/framework-tools": "
|
|
55
|
+
"@cedarjs/framework-tools": "2.5.1-next.27",
|
|
56
56
|
"@supabase/ssr": "0.8.0",
|
|
57
57
|
"@supabase/supabase-js": "2.93.3",
|
|
58
58
|
"@types/react": "^18.2.55",
|
|
@@ -69,5 +69,5 @@
|
|
|
69
69
|
"publishConfig": {
|
|
70
70
|
"access": "public"
|
|
71
71
|
},
|
|
72
|
-
"gitHead": "
|
|
72
|
+
"gitHead": "4a00a56324db4db5db1559e21850f4d9b5856b52"
|
|
73
73
|
}
|