This is a Next.js boilerplate project bootstrapped with create-next-app with the additions of typescript, eslint, storybook, prettier, sass, testing-library ,and jest.
Initialize a new next-app with this project as a template by running
npx create next-app --example https://github.com/datadeque/next-app
# or
yarn create next-app --example https://github.com/datadeque/next-appThis project uses yarn and is developed & maintained for node version 17+ (however CI will try builds using versions 12, 14, and 16 as well).
The recommended code editor is vscode along with the following extensions (see .vscode/extensions.json):
- eslint (Linter)
- prettier (Formatter)
- mdx (Syntax Highlighting for Storybook)
These extensions are highly recommended along with vscode because the project is pre-configured to format and fix ALL fixable issues on save. Furthermore, please open this project by running code . in the root directory from your terminal since there are known issues with environment variables when opening the project from gui.
First, install the dependencies by running yarn, then start the development server by running
yarn devOpen http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.
To start storybook development server by running
yarn storybookOpen http://localhost:6006/ with your browser and see the result.
You can lint the entire project using the built-in eslint config by running
yarn lintThis is the same command that runs during the lint step of the initial CI.
You can run your test files by running
yarn testThis is the same command that runs during the test step of the initial CI.
Every react component should atleast have one test, to see if it renders. Test files are to be placed in __test__ and follow the same file structure as the project root.
Suppose you built a new component under src/components/button/button.tsx, a test should be placed in __tests__/components/button/button.test.tsx with the following:
import { render } from '@testing-library/react'
import Button from 'components/button'
describe('Button', () => {
it('renders', () => {
render(<Button />)
})
})This will ensure that future modifications by others won't severely break your component. Should you have a complex component that interacts with its props, you should add some more complex tests.
Below is the an example of a recommended file structure:
src/
pages/
components/
ComponentName/
ComponentName.tsx
index.tsx
styles.scss # Modular Styles if needed
index.tsx
styles/
contexts/
hooks/
utils/
This project is has the following pre-configuration, which tests, lints and builds all branches and PRs.
name: CI
on:
push:
pull_request:
branches: ['**']
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
- run: yarn
- run: yarn test
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
- run: yarn
- run: yarn lint
build:
runs-on: ubuntu-latest
strategy:
matrix:
node: ['12', '14', '16', '17']
name: Node ${{ matrix.node }} Build
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
with:
node-version: ${{ matrix.node }}
- run: yarn
- run: yarn buildTo 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!