Next.js 14 boilerplate with App Router support, Next Auth, TRPC, Tailwind CSS, and TypeScript β‘οΈ Prioritizing developer experience first: Next.js, TypeScript, ESLint, Prettier, Husky, Lint-Staged, Jest, Testing Library, Commitlint, VSCode, PostCSS, Tailwind CSS, Authentication with NextAuth, Storybook and more.
Clone this project and use it to create your own Next.js project. This project is a minimalistic boilerplate for Next.js with the following features:
Developer experience first, extremely flexible code structure and only keep what you need:
@
prefixBuilt-in feature from Next.js:
nvm install 20.12.2 && nvm use 20.12.2
Run the following command on your local environment:
git clone --depth=1 https://github.com/paalamugan/next14-biolerplate-with-next-auth.git my-project-name
cd my-project-name
pnpm install
.env.example
file to .env.local
and update the environment variables with your own values.cp .env.example .env.local
and update the environment variables with your own values.
Then, you can run the project locally in development mode with live reload by executing:
pnpm dev
Open http://localhost:3000 with your favorite browser to see your project.
.
βββ README.md # README file
βββ .github # GitHub folder
βββ .husky # Husky configuration
βββ .storybook # Storybook folder
βββ .vscode # VSCode configuration
βββ public # Public assets folder
βββ scripts # Scripts folder
βββ src
β βββ app # Next JS App (App Router)
β βββ components # React components
β βββ constants # constants folder
β βββ server # server folder
β βββ stores # Store folder (Zustand)
β βββ hooks # hooks folder
β | βββ react-client # client side hooks
β | βββ react-server # server side hooks
β | βββ react-generic # generic hooks (both client and server)
β βββ layouts # layouts folder
β βββ lib # 3rd party libraries configuration
β βββ providers # providers folder
β βββ styles # Styles folder
β βββ templates # Templates folder
β βββ trpc # tRPC folder
β βββ types # Type definitions
β βββ utils # Utilities folder
β βββ validations # Validation schemas(Zod)
βββ tests
β βββ e2e # E2E tests, also includes Monitoring as Code
β βββ integration # Integration tests
βββ tailwind.config.js # Tailwind CSS configuration
βββ tsconfig.json # TypeScript configuration
You can easily configure Next js Boilerplate by making a search in the whole project with FIXME:
for making quick customization. Here is some of the most important files to customize:
public/apple-touch-icon.png
, public/favicon.ico
, public/favicon-16x16.png
and public/favicon-32x32.png
: your website favicon, you can generate from https://favicon.io/favicon-converter/src/constants/appConfig.ts
: configuration filesrc/templates/BaseTemplate.tsx
: default themenext.config.mjs
: Next.js configuration.env
: default environment variablesYou have access to the whole code source if you need further customization. The provided code is only example for you to start your project. The sky is the limit π.
The project enforces Conventional Commits specification. This means that all your commit messages must be formatted according to the specification. To help you write commit messages, the project uses Commitizen, an interactive CLI that guides you through the commit process. To use it, run the following command:
pnpm commit
One of the benefits of using Conventional Commits is that it allows us to automatically generate a CHANGELOG
file. It also allows us to automatically determine the next version number based on the types of commits that are included in a release.
All unit tests are located with the source code inside the same directory. So, it makes it easier to find them. The project uses Jest and React Testing Library for unit testing. You can run the tests with:
pnpm test
The project uses Playwright for Integration and E2E testing. You can run the tests with:
npx playwright install # Only for the first time in a new environment
pnpm test:e2e
The App Router folder is compatible with the Edge runtime. You can enable it by uncommenting the following lines src/app/layout.tsx
:
// export const runtime = 'edge';
Then, you can generate a production build with:
pnpm build
It generates an optimized production build of the boilerplate. For testing the generated build, you can run:
pnpm start
The command starts a local server with the production build. Then, you can now open http://localhost:3000 with your favorite browser to see the project.
Next.js Boilerplate comes with a built-in bundle analyzer. It can be used to analyze the size of your JavaScript bundles. To begin, run the following command:
pnpm build-stats
By running the command, it'll automatically open a new browser window with the results.
If you are VSCode users, you can have a better integration with VSCode by installing the suggested extension in .vscode/extension.json
. The starter code comes up with Settings for a seamless integration with VSCode. The Debug configuration is also provided for frontend and backend debugging experience.
With the plugins installed on your VSCode, ESLint and Prettier can automatically fix the code and show you the errors. Same goes for testing, you can install VSCode Jest extension to automatically run your tests and it also show the code coverage in context.
Pro tips: if you need a project wide type checking with TypeScript, you can run a build with Cmd
+ Shift
+ B
on Mac.
Licensed under the MIT License, Copyright Β© 2024
See LICENSE for more information.