-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node.js v14 Warning: Accessing non-existent property ___ of module exports inside circular dependency #2648
Comments
It looks like this is related to nodejs/node#32987. |
It seems that this is due to one of the dependencies we use. We will wait for patch version shelljs/shelljs#991 |
Coincidentally, the same question to me. When i change the NodeJs's version to 13.13.0, the problem disappear. |
node -v v14.0.0 I am trying to deploy my blog .md files to git pages. I got the following messages after running |
Docusaurus is not Hexo. |
Could you please help fix the following issues ?. Thank you
|
same here with mongodb - (node:9736) Warning: Accessing non-existent property 'count' of module exports inside circular dependency everything works though... |
@userqin @arieller This is the repository for Docusaurus, NOT MongoDB or Hexo. Please create or search on issues on those repositories for support. This is not the correct place to post these questions. @lex111 Might be worth deleting the comments above since they aren't relevant and off topic, as well as considering locking this thread. |
🐛 Bug Report
On Node.js v14 there are a lot of warnings when using docusaurus v2. These warnings do not occur when running Node.js v13.13.0.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
npm start
on a docusaurus v2 project (looks like it occurs onnpm run build
as well, maybe others)Expected behavior
No warnings or errors to occur in Node.js v14.0.0 (ie. same behavior as Node.js v13.13.0)
Actual Behavior
Lots of warnings displayed (see logs below).
Your Environment
Reproducible Demo
cd docs
npm install
npm start
The text was updated successfully, but these errors were encountered: