@supabase/gotrue-js 2.119.0-canary.2 → 2.119.0-canary.3

package/dist/main/GoTrueClient.d.ts

@@ -458,7 +458,7 @@ export default class GoTrueClient {
      * Be aware that you may get back an error message that will not distinguish
      * between the cases where the account does not exist or that the
      * email/phone and password combination is wrong or that the account can only
-     * be accessed via social login.
+     * be accessed via social sign-in.
      *
      * @category Auth
      *
@@ -592,7 +592,7 @@ export default class GoTrueClient {
      * @category Auth
      *
      * @remarks
-     * - This method is used for signing in using [Social Login (OAuth) providers](/docs/guides/auth#configure-third-party-providers).
+     * - This method is used for signing in using [social sign-in (OAuth) providers](/docs/guides/auth/social-sign-in).
      * - It works by redirecting your application to the provider's authorization screen, before bringing back the user to your app.
      *
      * @example Sign in using a third-party provider
@@ -1045,7 +1045,7 @@ export default class GoTrueClient {
      *
      * Be aware that you may get back an error message that will not distinguish
      * between the cases where the account does not exist or, that the account
-     * can only be accessed via social login.
+     * can only be accessed via social sign-in.
      *
      * Do note that you will need to configure a Whatsapp sender on Twilio
      * if you are using phone sign in with the 'whatsapp' channel. The whatsapp

package/dist/main/GoTrueClient.js

@@ -800,7 +800,7 @@ class GoTrueClient {
      * Be aware that you may get back an error message that will not distinguish
      * between the cases where the account does not exist or that the
      * email/phone and password combination is wrong or that the account can only
-     * be accessed via social login.
+     * be accessed via social sign-in.
      *
      * @category Auth
      *
@@ -987,7 +987,7 @@ class GoTrueClient {
      * @category Auth
      *
      * @remarks
-     * - This method is used for signing in using [Social Login (OAuth) providers](/docs/guides/auth#configure-third-party-providers).
+     * - This method is used for signing in using [social sign-in (OAuth) providers](/docs/guides/auth/social-sign-in).
      * - It works by redirecting your application to the provider's authorization screen, before bringing back the user to your app.
      *
      * @example Sign in using a third-party provider
@@ -1783,7 +1783,7 @@ class GoTrueClient {
      *
      * Be aware that you may get back an error message that will not distinguish
      * between the cases where the account does not exist or, that the account
-     * can only be accessed via social login.
+     * can only be accessed via social sign-in.
      *
      * Do note that you will need to configure a Whatsapp sender on Twilio
      * if you are using phone sign in with the 'whatsapp' channel. The whatsapp
@@ -3541,9 +3541,9 @@ class GoTrueClient {
      * ```
      *
      * @exampleDescription Store OAuth provider tokens on sign in
-     * When using [OAuth (Social Login)](/docs/guides/auth/social-login) you sometimes wish to get access to the provider's access token and refresh token, in order to call provider APIs in the name of the user.
+     * When using [OAuth (social sign-in)](/docs/guides/auth/social-sign-in) you sometimes wish to get access to the provider's access token and refresh token, in order to call provider APIs in the name of the user.
      *
-     * For example, if you are using [Sign in with Google](/docs/guides/auth/social-login/auth-google) you may want to use the provider token to call Google APIs on behalf of the user. Supabase Auth does not keep track of the provider access and refresh token, but does return them for you once, immediately after sign in. You can use the `onAuthStateChange` method to listen for the presence of the provider tokens and store them in local storage. You can further send them to your server's APIs for use on the backend.
+     * For example, if you are using [Sign in with Google](/docs/guides/auth/social-sign-in/auth-google) you may want to use the provider token to call Google APIs on behalf of the user. Supabase Auth does not keep track of the provider access and refresh token, but does return them for you once, immediately after sign in. You can use the `onAuthStateChange` method to listen for the presence of the provider tokens and store them in local storage. You can further send them to your server's APIs for use on the backend.
      *
      * Finally, make sure you remove them from local storage on the `SIGNED_OUT` event. If the OAuth provider supports token revocation, make sure you call those APIs either from the frontend or schedule them to be called on the backend.
      *

package/dist/main/lib/types.d.ts

@@ -1737,7 +1737,7 @@ export interface GoTrueMFAApi {
      * Returns the Authenticator Assurance Level (AAL) for the active session.
      *
      * - `aal1` (or `null`) means that the user's identity has been verified only
-     * with a conventional login (email+password, OTP, magic link, social login,
+     * with a conventional login (email+password, OTP, magic link, social sign-in,
      * etc.).
      * - `aal2` means that the user's identity has been verified both with a conventional login and at least one MFA factor.
      *

package/dist/main/lib/version.d.ts

@@ -1,2 +1,2 @@
-export declare const version = "2.119.0-canary.2";
+export declare const version = "2.119.0-canary.3";
 //# sourceMappingURL=version.d.ts.map

package/dist/main/lib/version.js

@@ -7,5 +7,5 @@ exports.version = void 0;
 // - Debugging and support (identifying which version is running)
 // - Telemetry and logging (version reporting in errors/analytics)
 // - Ensuring build artifacts match the published package version
-exports.version = '2.119.0-canary.2';
+exports.version = '2.119.0-canary.3';
 //# sourceMappingURL=version.js.map

package/dist/module/GoTrueClient.d.ts

@@ -458,7 +458,7 @@ export default class GoTrueClient {
      * Be aware that you may get back an error message that will not distinguish
      * between the cases where the account does not exist or that the
      * email/phone and password combination is wrong or that the account can only
-     * be accessed via social login.
+     * be accessed via social sign-in.
      *
      * @category Auth
      *
@@ -592,7 +592,7 @@ export default class GoTrueClient {
      * @category Auth
      *
      * @remarks
-     * - This method is used for signing in using [Social Login (OAuth) providers](/docs/guides/auth#configure-third-party-providers).
+     * - This method is used for signing in using [social sign-in (OAuth) providers](/docs/guides/auth/social-sign-in).
      * - It works by redirecting your application to the provider's authorization screen, before bringing back the user to your app.
      *
      * @example Sign in using a third-party provider
@@ -1045,7 +1045,7 @@ export default class GoTrueClient {
      *
      * Be aware that you may get back an error message that will not distinguish
      * between the cases where the account does not exist or, that the account
-     * can only be accessed via social login.
+     * can only be accessed via social sign-in.
      *
      * Do note that you will need to configure a Whatsapp sender on Twilio
      * if you are using phone sign in with the 'whatsapp' channel. The whatsapp

package/dist/module/GoTrueClient.js

@@ -797,7 +797,7 @@ class GoTrueClient {
      * Be aware that you may get back an error message that will not distinguish
      * between the cases where the account does not exist or that the
      * email/phone and password combination is wrong or that the account can only
-     * be accessed via social login.
+     * be accessed via social sign-in.
      *
      * @category Auth
      *
@@ -984,7 +984,7 @@ class GoTrueClient {
      * @category Auth
      *
      * @remarks
-     * - This method is used for signing in using [Social Login (OAuth) providers](/docs/guides/auth#configure-third-party-providers).
+     * - This method is used for signing in using [social sign-in (OAuth) providers](/docs/guides/auth/social-sign-in).
      * - It works by redirecting your application to the provider's authorization screen, before bringing back the user to your app.
      *
      * @example Sign in using a third-party provider
@@ -1780,7 +1780,7 @@ class GoTrueClient {
      *
      * Be aware that you may get back an error message that will not distinguish
      * between the cases where the account does not exist or, that the account
-     * can only be accessed via social login.
+     * can only be accessed via social sign-in.
      *
      * Do note that you will need to configure a Whatsapp sender on Twilio
      * if you are using phone sign in with the 'whatsapp' channel. The whatsapp
@@ -3538,9 +3538,9 @@ class GoTrueClient {
      * ```
      *
      * @exampleDescription Store OAuth provider tokens on sign in
-     * When using [OAuth (Social Login)](/docs/guides/auth/social-login) you sometimes wish to get access to the provider's access token and refresh token, in order to call provider APIs in the name of the user.
+     * When using [OAuth (social sign-in)](/docs/guides/auth/social-sign-in) you sometimes wish to get access to the provider's access token and refresh token, in order to call provider APIs in the name of the user.
      *
-     * For example, if you are using [Sign in with Google](/docs/guides/auth/social-login/auth-google) you may want to use the provider token to call Google APIs on behalf of the user. Supabase Auth does not keep track of the provider access and refresh token, but does return them for you once, immediately after sign in. You can use the `onAuthStateChange` method to listen for the presence of the provider tokens and store them in local storage. You can further send them to your server's APIs for use on the backend.
+     * For example, if you are using [Sign in with Google](/docs/guides/auth/social-sign-in/auth-google) you may want to use the provider token to call Google APIs on behalf of the user. Supabase Auth does not keep track of the provider access and refresh token, but does return them for you once, immediately after sign in. You can use the `onAuthStateChange` method to listen for the presence of the provider tokens and store them in local storage. You can further send them to your server's APIs for use on the backend.
      *
      * Finally, make sure you remove them from local storage on the `SIGNED_OUT` event. If the OAuth provider supports token revocation, make sure you call those APIs either from the frontend or schedule them to be called on the backend.
      *

package/dist/module/lib/types.d.ts

@@ -1737,7 +1737,7 @@ export interface GoTrueMFAApi {
      * Returns the Authenticator Assurance Level (AAL) for the active session.
      *
      * - `aal1` (or `null`) means that the user's identity has been verified only
-     * with a conventional login (email+password, OTP, magic link, social login,
+     * with a conventional login (email+password, OTP, magic link, social sign-in,
      * etc.).
      * - `aal2` means that the user's identity has been verified both with a conventional login and at least one MFA factor.
      *

package/dist/module/lib/version.d.ts

@@ -1,2 +1,2 @@
-export declare const version = "2.119.0-canary.2";
+export declare const version = "2.119.0-canary.3";
 //# sourceMappingURL=version.d.ts.map

package/dist/module/lib/version.js

@@ -4,5 +4,5 @@
 // - Debugging and support (identifying which version is running)
 // - Telemetry and logging (version reporting in errors/analytics)
 // - Ensuring build artifacts match the published package version
-export const version = '2.119.0-canary.2';
+export const version = '2.119.0-canary.3';
 //# sourceMappingURL=version.js.map