You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 26, 2023. It is now read-only.
Using app directory and layout could help improving page loading significantly, since it can allow dynamicly load large libs like plyr, pdfjs, etc based on specific path. Currently we have to load everything since the website can't know the content for certain path ahead of time.
Would you be interested in accepting PR regarding app directory refactoring, or collabrate on such refactoring in the future? I think the fetch API refactoring on API route is the first step towards this goal, since the new data fetching system for server components is built on top of the native fetch() Web API.
one potential objective: app/route in favor of pages/api (available in nextjs 13.1.7, currently in canary)
Note
route handler implement an isomorphic API to support both Edge and Node.js runtimes so functions like ResponseCompat and NodeRequsetToWeb is no longer required.
The text was updated successfully, but these errors were encountered: