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

Warning: Accessing non-existent property '__esModule' of module exports inside circular dependency #887

Closed
acanyon opened this issue Apr 27, 2020 · 5 comments

Comments

@acanyon
Copy link

acanyon commented Apr 27, 2020

On heroku I'm getting this error of module exports inside circular dependency. It appears to work locally though.

It never actually runs the migrations.

Any ideas?

$ heroku run sequelize db:migrate
Running sequelize db:migrate on ⬢ trendmobile... up, run.8730 (Hobby)

Sequelize CLI [Node: 14.0.0, CLI: 5.5.1, ORM: 5.21.6]

(node:4) Warning: Accessing non-existent property '__esModule' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:4) Warning: Accessing non-existent property '__esModule' of module exports inside circular dependency
(node:4) Warning: Accessing non-existent property '__esModule' of module exports inside circular dependency
(node:4) Warning: Accessing non-existent property '__esModule' of module exports inside circular dependency
(node:4) Warning: Accessing non-existent property '__esModule' of module exports inside circular dependency
(node:4) Warning: Accessing non-existent property '__esModule' of module exports inside circular dependency
(node:4) Warning: Accessing non-existent property '__esModule' of module exports inside circular dependency
(node:4) Warning: Accessing non-existent property '__esModule' of module exports inside circular dependency
Loaded configuration file "database/config/config.js".
Using environment "production".
@japel
Copy link

japel commented Apr 28, 2020

happens also for me with Node 14... with Node 12.x it works fine

@fuzunspm
Copy link

same issue here with node 14

@Swapnull
Copy link

This is a problem with node 14 - nodejs/node#33048
It has been fixed and will be released as part of the 14.1.0 release - nodejs/node#33103

@papb
Copy link
Member

papb commented Apr 29, 2020

Yes, precisely! Thanks @Swapnull! Node v14.1.0 has been released:

module: do not warn when accessing __esModule of unfinished exports (Anna Henningsen) #33048

@papb papb closed this as completed Apr 29, 2020
@acanyon
Copy link
Author

acanyon commented Apr 30, 2020

Thanks!

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

5 participants