71d1d363ad
* Update all dependencies and remove redundant ones from package.json. (60f9ee5) * Fixes #5596 by adjusting nodemon scripts (d4b7d3a) * Fixes `npm start` on windows by using `cross-env` (9555217) * Move compiled server out from `.next`. Compiling other JS into `.next` seems incorrect. (79fce02, 9ce7086) * Partly fixes #5753 by making sure typescript compiles with `es2017` as target, at least ensuring code is runnable on node 8. Previously it was compiled with `esnext`. (9176e92) --- I tried improving the structure by keeping source in `src/app` and `src/server` and then building to `dist/server` and `dist/app` but I didn't really get it to work and made most configs more complicated. Moved the built server out from `.next` anyway. |
||
|---|---|---|
| .. | ||
| 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.