Question about nextjs..
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 11.8k
- 分支
- 7.9k
- 平均合併
- 1 天 11 小時
- 30 天內合併 PR
- 11
描述
After using nextjs, the page movement time is very slow. I know React pushes nextjs, but when using react, I moved the page right away, but in nextjs, it feels like it moves too slowly. I doubt if ssr is the best. I think that csr should be selected separately or a better alternative should be created.
And there was a time when a custom was needed at the time of the route, but this is too internal, so it is a problem how to set it up. This developed an in-depth custom route according to the customer's requirements, but in nextjs, there are times when you can't get a sense of the implementation direction. What I'm talking about is customization. It's best to keep this as open as possible.
I use createElement and croneElement very usefully, but I was embarrassed to see that they were registered as legacy on the new React page. This is very useful for free customization.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
此 issue 提到了 Next.js、React、SSR、CSR、routing 和 createElement,但沒有指出任何檔案、測試或進入點。首先釐清請求涉及 React 文件網站還是 Next.js 的行為,然後在實作之前定義一項具體且可測試的文件變更。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript, nextjs, react
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 15/100