one-aalam / next-starter-kit

Next.js with brilliant bells and useful whistles

Next.js Starter Kit

Boilerplate to quckly get up and running with Next.js with

• Typescript as the language choice
• Tailwind CSS for quick styling without getting out of your HTML
• ESLint for static code analysis
• Prettier for code formatting
• SEO pre-configured
• Icons & SVG support out of the box

and pre-made

• Message/Alerts `coz who don't uses one?
• Authentication system with Supabase In the with-supabase branch

Getting Started

First, run the development server:

npm run dev
# or
yarn dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.js. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in src/pages/api/hello.ts.

The src/pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

Learn More

To learn more about Next.js, take a look at the following resources:

• Next.js Documentation - learn about Next.js features and API.
• Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

next-starter-kit's Issues

Forgot Password

Would be great to see if you could add a Forgot Password option.

Cookie and sessions out of sync

Hello,

This is a wonderful starter kit, exactly the stack I use! Thank you for this, as it has made my life much easier.

I have an issue with the user / auth part in your Supabase branch. It seems that our AuthContext provider gets out of sync with the server. right now, after logging in, we store the user and session in formation use useStore. At the same time, we do the authentication on the server side and for page access lever using getUserByCookie. These two seem to go out of sync after the cookie expires, as I can still access the user information using the sser and session conext, but supabase.auth.api.getUserByCookie returns null.