Question 1

How do I add Google OAuth to nextjs-starter?

Accepted Answer

You need to manually configure NextAuth.js by adding Google provider credentials to the environment variables and updating the API routes, as it's not included by default. Refer to NextAuth.js documentation for specific steps, but be prepared to modify the authentication setup.

Question 2

Can I use MongoDB instead of Fauna DB with this starter?

Accepted Answer

Switching to MongoDB requires significant rework, as the starter is tightly integrated with Fauna's schema and migration tools. You'd need to replace database queries, remove Fauna dependencies, and set up a new database connection, which defeats the purpose of using this boilerplate.

Question 3

How to deploy nextjs-starter to Netlify since the guide is TBD?

Accepted Answer

Since the README lacks deployment instructions, you'll need to adapt general Next.js Netlify deployment guides, ensuring environment variables are set and the build configuration aligns with the starter's dependencies. This may involve trial and error due to the missing documentation.

Question 4

Is nextjs-starter better than using create-next-app with manual setup?

Accepted Answer

nextjs-starter saves time if you need its specific stack (Fauna, NextAuth, React Query), but create-next-app offers more flexibility for custom tooling. Choose this starter only if you're committed to its pre-configured choices; otherwise, manual setup allows finer control.

Question 5

How to customize the authentication flow in nextjs-starter?

Accepted Answer

You can modify the NextAuth.js configuration in the API routes to adjust callbacks, sessions, or UI, but changes may break existing integrations. Since it's pre-configured, deep customization requires understanding of NextAuth.js internals and careful testing.

nextjs-starter

What is nextjs-starter?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions