Comments (10)
Apparently this warning was also there in v18.2 😅
Will be fixed in v3.3.1 thanks to #10103
from docusaurus.
This is fixed for the next release, planned for tomorrow.
Until then you can downgrade to React 18.2 which does not have this warning
from docusaurus.
@slorber thank you for the fast response. In this case please feel free to close this issue.
I can hide error logs in the console if they annoy me.
No worries. These things happen in this fast evolving landscape.
But tomorrow it'll be fixed.. Promise? No Backsies 🤣
from docusaurus.
Yes it will be fixed today, working on it right now. (#10101)
Note you are using Chrome 89, a quite old version that's probably why StackBlitz does not work.
Warning: You are calling ReactDOMClient.createRoot() on a container that has already been passed to createRoot() before. Instead, call root.render() on the existing root instead if you want to update it.
I am unable to reproduce this warning and did not do anything to fix it.
If you can still reproduce it, please tell me the exact steps, including how you run Docusaurus and which page exactly you see the error on (including how you opened that page, between a browser page load or a navigation action). This issue does not contain those details atm but they are important to figure out problems.
from docusaurus.
@slorber thx for the update. I can confirm that most warnings are gone on v3.3.0 ❤️.
I still get this warning ReactDOMClient.createRoot()
, it happens on hot-reloading.
I'll try to reproduce it on a clean MVP project and send you the github repo if I can reproduce it there.
Thanks so far. Super helpful.
from docusaurus.
@slorber
I just tested it in a completely clean instance (no modifications).
You can just do the following:
- run
npx create-docusaurus@latest docusaurus-demo classic
- update to react
18.3.1
- update to docusaurus
3.3.0
- run
npm start
- open web console
- go to index.tsx and change adjust the text
- see console error
If it helps, I can upload the repo but the steps above should be super clear and probably just as easy as cloning a repo with those adjustments already in place.
from docusaurus.
@slorber BTW. I am not using v89 of chrome 🤣 that is the example that was provided by your issue template. I just added v20 of Node after the colon and did not mention the chrome version at all as it was irrelevant to this issue.
Environment name and version (e.g. Chrome 89, Node.js 16.4): Node v20
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Unrelated (using Windows 11)
I guess you are referring to this (e.g. Chrome 89, Node.js 16.4)
Maybe it is wiser to put the example text in an HTML comment instead of parentheses, to prevent this misunderstanding in future bug reports.
from docusaurus.
https://github.com/pixelass/docusaurus-bug-report-000001
MVP reproduction for the issue on hot-reloading
You can just do the following:
- clone the repoitory
- run
npm i
oryarn
- run
npm start
oryarn start
- open web console
- go to index.tsx and change any text and save
- see console error
from docusaurus.
THanks yes, I can reproduce now.
I'll have to publish a v3.3.1 soon then 😅
from docusaurus.
Community is everything 😄
from docusaurus.
Related Issues (20)
- Unable to set a breakpoint in code in Chrome/Firefox HOT 4
- Page loses scrollbar when using Algolia search bar HOT 1
- With trailingSlash:true serving a build/ gives site did not load properly HOT 1
- <span style="color:orange"> in Markdown causes build to fail HOT 2
- Invalid modification of Webpack's build configuration HOT 6
- Script attribute value with quotes is escaped HOT 8
- The Markdown front matter field "id" in the index.md file under the category is ignored HOT 3
- Add option to not show the date on blog posts HOT 3
- Markdown relative links are treated URL paths if split over multiple lines HOT 1
- Console log with 188 error when using with webserver after Cloudflare HOT 2
- How to disable static site generation and SEO metadata
- RFC: Blog authors pages HOT 1
- [Docusaurus v3.4] index.html in static directory raises "Multiple assets emit different content to the same filename" error HOT 2
- The "paths[1]" argument must be of type string. HOT 20
- [ERROR] TypeError [ERR_INVALID_ARG_TYPE]: The "paths[1]" argument must be of type string. Received undefined HOT 2
- Support image resize
- Clicking "current version" at the version dropdown redirects to the landing page of docs, which is unintuitive HOT 2
- Insecure NPM packages Detected in Docusaurus Core as a Nested Dependency HOT 1
- Webpack dev server fails to start without static assets HOT 2
- Ideal image flashing when navigating back and forward
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docusaurus.