Login

Nexty.dev's login functionality is built on Supabase Auth. We chose Supabase Auth because it's one of the options that minimizes cognitive load for developers:

• Simple configuration - even without a technical background, following the Supabase Integration Documentation won't lead to errors
• Supabase Auth has built-in token and cookie management mechanisms, which are crucial for platform stability and security - now you don't need to spend time on this at all
• Perfect integration with Supabase database, easily handling database access permission control

Supported Login Methods

For products targeting global operations, Google OAuth and email login are unavoidable. If your product also hopes to attract developers' attention, then GitHub OAuth is also an important choice. Therefore, Nexty.dev supports these three login methods by default: Google OAuth, GitHub OAuth, and email Magic Link.

Supabase Auth supports numerous mainstream third-party logins, including Apple, Azure (Microsoft), Discord, Facebook, Notion, and more. Once you master the configuration methods for GitHub and Google OAuth, adding login methods for other platforms becomes effortless.

Email Alias Filtering

The lib/email.ts file in Nexty source code contains two important methods: email validation (validateEmail) and email alias filtering (normalizeEmail). These two methods can help prevent risks from abnormal emails and email aliases to some extent.

Many users may not know that email services like Gmail and Outlook support adding prefixes and suffixes as aliases. For SaaS products offering free trials, this could lead to users registering unlimited accounts through email aliases to obtain trial benefits.

In components/providers/AuthProvider.tsx, we filter out these email aliases through the normalizeEmail method:

const signInWithEmail = async (email: string) => {
  return await supabase.auth.signInWithOtp({
    email: normalizeEmail(email), // Filter email aliases
    // ... omitted ...
  });
};