05ddf3e4e0
I noticed that the nodemon.json file was not watching for all file changes in the correct location for filetype .ts (typescript). After some research I found that the "ext" option in the nodemon.json fixes the issue and should work across all operating systems. |
||
|---|---|---|
| .. | ||
| pages | ||
| server | ||
| .babelrc | ||
| .gitignore | ||
| next.config.js | ||
| nodemon.json | ||
| package.json | ||
| README.md | ||
| tsconfig.json | ||
| tsconfig.server.json | ||
Custom server with TypeScript + Nodemon example
How to use
Using create-next-app
Execute create-next-app with Yarn or npx to bootstrap the example:
npx create-next-app --example custom-server-typescript custom-server-typescript-app
# or
yarn create next-app --example custom-server-typescript custom-server-typescript-app
Download manually
Download the example:
curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/custom-server-typescript
cd custom-server-typescript
Install it and run:
npm install
npm run dev
# or
yarn
yarn dev
Deploy it to the cloud with now (download)
now
The idea behind the example
The example shows how you can use TypeScript on both the server and the client while using Nodemon to live reload the server code without affecting the Next.js universal code.
Server entry point is server/index.ts in development and production-server/index.js in production.
The second directory should be added to .gitignore.