.
├── README.md
├── pages
│ └── index.js
| └── episode
| └── [id].js
├── src
│ ├── components
│ └── features
| └── Player
| └── components
| └── index.js
├── node_modules
│ ├── [...]
├── package.json
├── static
│ └── favicon.ico
└── yarn.lock
Routing in Next.js is based on the file system, so ./pages/index.js maps to the / route and ./pages/about.js would map to /about.
The ./static directory maps to /static in the next server, so you can put all your other static resources like images or compiled CSS in there.
Out of the box, we get:
- Automatic compilation and bundling (with Babel and webpack)
- Hot code reloading
- Server rendering and indexing of
./pages/ - Static file serving.
./static/is mapped to/static/
Read more about Next's Routing
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any errors in the console.
Builds the app for production to the .next folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
Starts the application in production mode. The application should be compiled with next build first.
See the section in Next docs about deployment for more information.