Starter template for building a project using React, Typescript, Next.js, Jest, ChakraUI and ESLint.
- Clone or download the project.
cd
in the project directory.- If you cloned the project, make sure you remove the remote reference to this project by running
git remote rm origin
. - Copy
.env.example
to.env
as that file is used to load up all your environment variables. - Run
yarn install
ornpm install
to install all dependencies.
-
yarn dev
: To start a local development server. -
yarn test
: To run the entire unit test suite usingjest
. -
yarn test:ci
: To run tests on CI. -
yarn lint
: To run the ESLint based linter to find out the issues in the project. -
yarn lint:fix
: To autoformat all the issues. -
yarn export
: Run this after runningyarn analyze
to export a build copy. -
yarn production
: To export a production build. Useyarn start
to serve that. -
yarn upgrade --latest
: To upgrade all packages to their latest versions (could include breaking changes).
All source code is located in the src/
directory:
-
All Next.js entrypoints are housed in the
src/pages
directory as a default.- Currently has
_app.tsx
which bootstraps ChakraUI within this project. - There's also a sample
index.tsx
.
NOTE: Feel free to move
pages
outside ofsrc/
if that's what you prefer. You'll just need to restart your local development server and everything should continue working as normal. - Currently has
-
src/components
are all stateless reusable components.- Includes a dummy
MainHeading
component with a JEST test as a sample. Feel free to delete this.
- Includes a dummy
-
src/styles
folder is there just to house any styling.- It currently contains the ChakraUI theme ready for you to extend. This file has already been imported in
_app.tsx
and is already supplied as a prop toChakraProvider
.
- It currently contains the ChakraUI theme ready for you to extend. This file has already been imported in
-
All env variables are available in
.env
files (.env
file isn't committed). Whenever you update.env
, please update.env.example
and.env.test
andnext.config.js
to proxy all environment variables properly.- You can access these variables in the app source code anywhere using
process.env.<VAR_NAME>
.
- You can access these variables in the app source code anywhere using
If you feel like changing the directory structure, please change the appropriate settings in the following files:
jest.config.js
tsconfig.json
- The
lint
and thelint:fix
scripts inpackage.json