[Feedback] Support/Docs for Next.js v16 "Cache Components"

未关闭
  • 哪里不对？
#349 2 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@dferber90 已经在做这个了。

开始于 2026年3月25日。

评估

这个 Issue 还没有评估数据。

描述

feedback

We have a Next.js site that currently is mostly statically rendered at build-time, and with an already fairly complex routing structure and proxy file, we're not interested in introducing more complexity via the precompute method this library provides.

Now that Next.js v16 is out and supports cache components (previously known as partial pre-rendering or PPR), it would be nice to have support for this alternate method of fetching flags in a static route.

We're considering loading flags on the client side at this time, as we can't see any functional difference to the end-user if an element pops into view via the server or a client fetch, aside from the fact that the server now has extra work to do, more costs for us etc. However this library, at least the Next.js adaptor, does not support the client side at all by default, which feels like a significant omission, especially before cache components were promoted to stable.

主要语言
TypeScript
星标
629
派生
93
平均合并
1 天 15 分钟
30 天内合并 PR
25

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

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

vercel/flags 的其他 Issue

查看 vercel/flags 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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