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
I have read the console error message carefully (if applicable).
Description
Recently, typescript-eslint updated docusaurus to the lastest version and there is an issue with infinite rendering when the url hash changed. (typescript-eslint/typescript-eslint#8736)
The problem occurs when a lazy loaded component within a <BrowserOnly/> changes the hash via useHistory's replace.
This is a simple reproduction: https://github.com/yeonjuan/docusaurus-bug-repro
yeonjuan
changed the title
BrowserOnly, lazy, and useHistory result in infinite rendering
BrowserOnly, lazy, and useHistory result in infinite re-rendering
Mar 22, 2024
Have you read the Contributing Guidelines on issues?
Prerequisites
npm run clear
oryarn clear
command.rm -rf node_modules yarn.lock package-lock.json
and re-installing packages.Description
Recently, typescript-eslint updated docusaurus to the lastest version and there is an issue with infinite rendering when the url hash changed. (typescript-eslint/typescript-eslint#8736)
The problem occurs when a lazy loaded component within a
<BrowserOnly/>
changes the hash viauseHistory's replace
.This is a simple reproduction: https://github.com/yeonjuan/docusaurus-bug-repro
When I add the code below at the parent of
<BrowserOnly/>
, it works well.Reproducible demo
No response
Steps to reproduce
Expected behavior
Infinite rendering should not occur
Actual behavior
Infinite rendering
Your environment
Self-service
The text was updated successfully, but these errors were encountered: