How to set up an enterprise Next.js stack
Configuring Next.js with TypeScript, ESLint & prettier can become really
annoying, especially if you're a beginner and don't know the intricate
details of all the moving parts in a web-dev environment. The most important
things you have to set up are:
- A working ESLint config
- Prettier plugins that auto-format your code
- Absolute imports
```
will be rendered like this:

If you don't need or want this dependency you can safely remove it.
## Extending the template
### Config files
| File name | What it does |
| ----------------------- | --------------------------------------------------------------------------------------------------------- |
| `tsconfig.json` | TypeScript configuration. Tells IDE which absolute imports exist and works in conjunction with .babelrc |
| `.eslintrc.json` | Config file for finding and fixing problems in code. E.g: No function should be used before it's defined. |
| `tailwind.config.js` | TailwindCSS config. Adds new sizes, shadows, borders etc. to your tailwind classes. |
| `postcss.config.js` | Tells your project to include TailwindCSS in build chain. |
| `prettier.config.js` | Rules for formatting your code. E.g: indent code 6 spaces instead of 4 |
| `.vscode/settings.json` | Custom settings for your VSCode workspace. Tells VSCode to auto-format code on save. |
### Changing the font
1. In `src/pages/_app.tsx` replace the link tag with your url (can be Google Fonts, Adobe Typekit, etc.)
```html