2ecf1b21ca
This means public/unlisted posts and the home-page are no longer generated at build-time, so TTFB may be increased for the first user to load/access a page. Cache-Control headers are set so if the RP / server supports it the results should be cached for future users. |
||
|---|---|---|
| .. | ||
| components | ||
| lib | ||
| pages | ||
| public | ||
| styles | ||
| .dockerignore | ||
| .env.local | ||
| .eslintrc.json | ||
| .gitignore | ||
| .prettierrc | ||
| Dockerfile | ||
| next-env.d.ts | ||
| next.config.mjs | ||
| package.json | ||
| postcss.config.json | ||
| README.md | ||
| tsconfig.json | ||
| yarn.lock | ||
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.
API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.ts.
The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.