250x250
Notice
Recent Posts
Recent Comments
Link
일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 |
Tags
- error
- graphQL
- concept
- blockchain
- bitcoin
- SSR
- 기준
- Redux
- JavaScript
- tailwindcss
- typeScript
- API
- CLASS
- Props
- web
- 삶
- nextJS
- express.js
- REACT
- HTML
- hardhat
- Interface
- evm
- useState
- node.js
- built in object
- middleware
- CSS
- solidity
- Ethereum
Archives
- Today
- Total
목록caching (1)
ReasonJun

Next.js has a default caching mechanism aimed at enhancing performance and cost-efficiency. By default, it employs static rendering for routes and caches data requests unless you specifically choose not to use caching. Here's a summary of the default caching behavior: Static Route Rendering: Routes are statically rendered at build time. This means that during the build process, Next.js generates..
Frontend/Next.js
2023. 9. 10. 23:39