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
The page(not only the official site, but also my blog site after updating to v8.19.0) is empty and I get two errors in Console.(All things normal, without errors in Console in v8.18.2)
Steps to reproduce the behavior
Visit the official site.
Update blog NexT version to v8.19.0
Node.js and NPM Information
v18.17.0
9.6.7
Package dependencies Information
Seems to be irrelevant. I'll add if necessary.
Hexo Configuration
Seems to be irrelevant. I'll add if necessary.
NexT Configuration
Seems to be irrelevant. I'll add if necessary.
Other Information
Today I visit the official documentation and find it displays nothing. Then I update NexT to v8.19.0 via git pull and get the same thing occurred in my blog. And everything back to normal after using git reset --hard v8.18.2. As a result, I think it may have some thing to do with the new released version.
Otherwise, if it is the issue of my network, just close this issue as invalid.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. It is possible issue was solved or at least outdated. Feel free to open new for related bugs.
Issue Checklist
Expected behavior
All things normal.
Actual behavior
The official site
The page(not only the official site, but also my blog site after updating to v8.19.0) is empty and I get two errors in Console.(All things normal, without errors in Console in v8.18.2)
Steps to reproduce the behavior
Node.js and NPM Information
Package dependencies Information
Hexo Configuration
Seems to be irrelevant. I'll add if necessary.
NexT Configuration
Seems to be irrelevant. I'll add if necessary.
Other Information
Today I visit the official documentation and find it displays nothing. Then I update NexT to v8.19.0 via
git pull
and get the same thing occurred in my blog. And everything back to normal after usinggit reset --hard v8.18.2
. As a result, I think it may have some thing to do with the new released version.Otherwise, if it is the issue of my network, just close this issue as invalid.
Thanks in advance!
The text was updated successfully, but these errors were encountered: