Skip to content

N
next.js

CoCo_Code_Op2 / next.js
与 Fork 源项目一致

从无法访问的项目Fork

通知 1
Star 0
Fork 0
N
next.js

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 12 9月, 2020 12 次提交
  3. 11 9月, 2020 11 次提交
  5. 10 9月, 2020 7 次提交
  7. 09 9月, 2020 5 次提交
    • J
      v9.5.4-canary.7 · fceb566b
      由 Joe Haddad 提交于
      fceb566b
    • G
      Remove `next-head-count` (#16758) · 039eb817
      由 Gerald Monaco 提交于 
      Removes `next-head-count`, improving support for 3rd party libraries that insert or append new elements to `<head>`.

---

This is more or less what a solution with a `data-` attribute would look like, except that instead of directly searching for elements with that attribute, we serialize the elements expected in `<head>` and then find them/assume ownership of them during initialization (in a manner similar to React's reconciliation) based on their properties.

There are two main assumptions here:
1. Content is served with compression, so duplicate serialization of e.g. inline script or style tags doesn't have a meaningful impact. Storing a hash would be a potential optimization.
2. 3rd party libraries primarily only insert new, unique elements to head. Libraries trying to actively manage elements that overlap with those that Next.js claims ownership of will still be unsupported.

The reason for this roundabout approach is that I'd really like to avoid `data-` if possible, for maximum compatibility. Implicitly adding an attribute could be a breaking change for some class of tools or crawlers and makes it otherwise impossible to insert raw HTML into `<head>`. Adding an unexpected attribute is why the original `class="next-head"` approach was problematic in the first place!

That said, while I don't expect this to be more problematic than `next-head-count` (anything that would break in this new model also should have broken in the old model), if that does end up being the case, it might make sense to just bite the bullet.

Fixes #11012
Closes #16707

---

cc @Timer @timneutkens
      039eb817
    • S
      Fix typo in Pet mongoose model (#16943) · 4ba3607d
      由 Sashank Thupukari 提交于 
      s/applicale/applicable/
      4ba3607d
    • T
      Fix align documentation with the code (#16843) · b2276919
      由 Turcan Vladimir 提交于
      b2276919
    • J
      Correct page path for GS(S)P data refreshing (#16939) · f46ddc69
      由 JJ Kasper 提交于 
      This makes sure to the page path is the expected version to trigger refreshing on the client and adds additional tests to make sure it is working properly with these page variants. 

Closes: https://github.com/vercel/next.js/issues/16938
      f46ddc69
  9. 08 9月, 2020 4 次提交
  11. 07 9月, 2020 1 次提交