reactjs / reactjs/react.dev

Question about nextjs..

未关闭
#6,079 2 条评论 3 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 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.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

该 issue 提到了 Next.js、React、SSR、CSR、routing 和 createElement,但没有指出任何文件、测试或入口点。首先明确请求涉及 React 文档网站还是 Next.js 的行为,然后在实现之前定义一项具体且可测试的文档变更。

由索引模型根据 Issue 内容生成。

评估

技术栈
javascript, nextjs, react
领域
documentation
Issue 类型
文档
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
需要澄清
新手友好度
15/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。