@cedarjs/auth-supabase-web 2.2.2-next.0 → 2.2.2-next.31

package/dist/cjs/index.js

@@ -16,11 +16,11 @@ var __copyProps = (to, from, except, desc) => {
   return to;
 };
 var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
-var index_exports = {};
-__export(index_exports, {
+var src_exports = {};
+__export(src_exports, {
   createAuth: () => import_supabase.createAuth
 });
-module.exports = __toCommonJS(index_exports);
+module.exports = __toCommonJS(src_exports);
 var import_supabase = require("./supabase.js");
 // Annotate the CommonJS export names for ESM import in node:
 0 && (module.exports = {

package/dist/cjs/supabase.js

@@ -70,65 +70,18 @@ function createAuthImplementation({
     login: async (credentials) => {
       let result;
       switch (credentials.authMethod) {
-        /**
-         * Log in an existing user with an email and password or phone and password.
-         *
-         * 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.
-         */
         case "password":
           result = await supabaseClient.auth.signInWithPassword(credentials);
           break;
-        /**
-         * Log in an existing user via a third-party provider.
-         */
         case "oauth":
           result = await supabaseClient.auth.signInWithOAuth(credentials);
           break;
-        /**
-         * Log in a user using magiclink or a one-time password (OTP).
-         *
-         * If the `{{ .ConfirmationURL }}` variable is specified in the email template, a magiclink will be sent.
-         * If the `{{ .Token }}` variable is specified in the email template, an OTP will be sent.
-         * If you're using phone sign-ins, only an OTP will be sent. You won't be able to send a magiclink for phone sign-ins.
-         *
-         * 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.
-         */
         case "otp":
           result = await supabaseClient.auth.signInWithOtp(credentials);
           break;
-        /**
-         * Attempts a single-sign on using an enterprise Identity Provider. A
-         * successful SSO attempt will redirect the current page to the identity
-         * provider authorization page. The redirect URL is implementation and SSO
-         * protocol specific.
-         *
-         * You can use it by providing a SSO domain. Typically you can extract this
-         * domain by asking users for their email address. If this domain is
-         * registered on the Auth instance the redirect will use that organization's
-         * currently active SSO Identity Provider for the login.
-         *
-         * If you have built an organization-specific login page, you can use the
-         * organization's SSO Identity Provider UUID directly instead.
-         *
-         * This API is experimental and availability is conditional on correct
-         * settings on the Auth service.
-         *
-         * @experimental
-         */
         case "sso":
           result = await supabaseClient.auth.signInWithSSO(credentials);
           break;
-        /**
-         * Allows signing in with an ID token issued by certain supported providers.
-         * The ID token is verified for validity and a new session is established.
-         *
-         * @experimental
-         */
         case "id_token":
           result = await supabaseClient.auth.signInWithIdToken(credentials);
           break;

package/dist/supabase.js

@@ -50,65 +50,18 @@ function createAuthImplementation({
     login: async (credentials) => {
       let result;
       switch (credentials.authMethod) {
-        /**
-         * Log in an existing user with an email and password or phone and password.
-         *
-         * 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.
-         */
         case "password":
           result = await supabaseClient.auth.signInWithPassword(credentials);
           break;
-        /**
-         * Log in an existing user via a third-party provider.
-         */
         case "oauth":
           result = await supabaseClient.auth.signInWithOAuth(credentials);
           break;
-        /**
-         * Log in a user using magiclink or a one-time password (OTP).
-         *
-         * If the `{{ .ConfirmationURL }}` variable is specified in the email template, a magiclink will be sent.
-         * If the `{{ .Token }}` variable is specified in the email template, an OTP will be sent.
-         * If you're using phone sign-ins, only an OTP will be sent. You won't be able to send a magiclink for phone sign-ins.
-         *
-         * 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.
-         */
         case "otp":
           result = await supabaseClient.auth.signInWithOtp(credentials);
           break;
-        /**
-         * Attempts a single-sign on using an enterprise Identity Provider. A
-         * successful SSO attempt will redirect the current page to the identity
-         * provider authorization page. The redirect URL is implementation and SSO
-         * protocol specific.
-         *
-         * You can use it by providing a SSO domain. Typically you can extract this
-         * domain by asking users for their email address. If this domain is
-         * registered on the Auth instance the redirect will use that organization's
-         * currently active SSO Identity Provider for the login.
-         *
-         * If you have built an organization-specific login page, you can use the
-         * organization's SSO Identity Provider UUID directly instead.
-         *
-         * This API is experimental and availability is conditional on correct
-         * settings on the Auth service.
-         *
-         * @experimental
-         */
         case "sso":
           result = await supabaseClient.auth.signInWithSSO(credentials);
           break;
-        /**
-         * Allows signing in with an ID token issued by certain supported providers.
-         * The ID token is verified for validity and a new session is established.
-         *
-         * @experimental
-         */
         case "id_token":
           result = await supabaseClient.auth.signInWithIdToken(credentials);
           break;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cedarjs/auth-supabase-web",
-  "version": "2.2.2-next.0+50c9164d3",
+  "version": "2.2.2-next.31+ff2776832",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/cedarjs/cedar.git",
@@ -49,10 +49,10 @@
     "test:watch": "vitest watch"
   },
   "dependencies": {
-    "@cedarjs/auth": "2.2.2-next.0+50c9164d3"
+    "@cedarjs/auth": "2.2.2-next.31+ff2776832"
   },
   "devDependencies": {
-    "@cedarjs/framework-tools": "2.2.2-next.1",
+    "@cedarjs/framework-tools": "2.2.2-next.31",
     "@supabase/ssr": "0.8.0",
     "@supabase/supabase-js": "2.87.3",
     "@types/react": "^18.2.55",
@@ -69,5 +69,5 @@
   "publishConfig": {
     "access": "public"
   },
-  "gitHead": "50c9164d38f49178f060177be747dd7c484d1e36"
+  "gitHead": "ff2776832afcb70cd4ca38986ec4e37043e1c44b"
 }