Skip to content
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

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

Closed
5 tasks done
himself65 opened this issue Jul 5, 2020 · 3 comments

Comments

@himself65
Copy link
Member

Check List

Please check followings before submitting a new issue.

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
Copy link
Member

stevenjoezhang commented Jul 5, 2020

It's caused by stylus, not Hexo

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

@himself65
Copy link
Member Author

Thanks.

Closing

@robpidev
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants