Accessing non-existent property 'xxx' of module exports inside circular dependency in Node.js 14.x

[himself65]

Check List

Please check followings before submitting a new issue.

• I have already read Docs page & Troubleshooting page
• I have already searched existing issues and they are not help to me
• I examined error or warning messages and it's difficult to solve
• Using the latest version of Hexo (run hexo version to check)
• Node.js is higher than minimum required version

Expected behavior

running without warnings.

Actual behavior

$ hexo server
(node:3524) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:3524) Warning: Accessing non-existent property 'column' of module exports inside circular dependency
(node:3524) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency
(node:3524) Warning: Accessing non-existent property 'lineno' of module exports inside circular dependency
(node:3524) Warning: Accessing non-existent property 'column' of module exports inside circular dependency
(node:3524) Warning: Accessing non-existent property 'filename' of module exports inside circular dependency
INFO  Start processing
INFO  Hexo is running at http://localhost:4000 . Press Ctrl+C to stop.

How to reproduce?

npm install -g hexo-cli
npx hexo init hexo-test
cd hexo-test
yarn server

Is the problem still there under "Safe mode"?

Environment & Settings

Node.js & npm version(node -v && npm -v)

PS C:\Users\Himself65\desktop\github\test\hexo-test> node -v
v14.5.0
PS C:\Users\Himself65\desktop\github\test\hexo-test> npm -v
6.14.5

Others

Node.js 14 landed a feature which will log when circular dependency

Refs: nodejs/node#32987

[stevenjoezhang]

It's caused by stylus, not Hexo

See also http://github.com/stylus/stylus/issues/2534
#4257

[himself65]

Thanks.

Closing

[robpidev]

I had the same error, but it is that you are calling said module itself or calling a module that depends on it, generating this in a loop, try to find said package