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

Package exports for '...\node_modules\uuid' do not define a valid '.' target. #12419

Closed
2 of 7 tasks
ynhhoJ opened this issue Jun 24, 2020 · 5 comments
Closed
2 of 7 tasks

Comments

@ynhhoJ
Copy link

ynhhoJ commented Jun 24, 2020

Issue Description

What do you expect to happen?

Run code without errorss.

What is actually happening?

Error: Package exports for '...\node_modules\uuid' do not define a valid '.' target.

Environment

  • Sequelize version: sequelize@6.0.0-beta.7
  • Node.js version: v13.13.0
  • Operating System: Windows 10
  • If TypeScript related: TypeScript version: 3.8.3

Issue Template Checklist

How does this problem relate to dialects?

  • I think this problem happens regardless of the dialect.
  • I think this problem happens only for the following dialect(s):
  • I don't know, I was using PUT-YOUR-DIALECT-HERE, with connector library version XXX and database version XXX

Would you be willing to resolve this issue by submitting a Pull Request?

  • Yes, I have the time and I know how to start.
  • Yes, I have the time but I don't know how to start, I would need guidance.
  • No, I don't have the time, although I believe I could do it if I had the time...
  • No, I don't have the time and I wouldn't even know how to start.
@sushantdhiman
Copy link
Contributor

Not related to Sequelize uuidjs/uuid#466

@ynhhoJ
Copy link
Author

ynhhoJ commented Jun 24, 2020

But in sequelize@6.0.0-beta.6 everything is okay

@sushantdhiman
Copy link
Contributor

Not sure but this is not related to Sequelize, try removing / reinstalling node_modules

@elmoura
Copy link

elmoura commented Aug 2, 2020

Hey there! I was having the same problem using the Node.js v13.1.0 version.

It looks like this error occurs at some not LTS versions of Node. I installed the v12.18.3 and it solved my problem.
Hope it helps you too.

@4ch1
Copy link

4ch1 commented Aug 12, 2020

Hi, I had the same problem using Node.js v13.0.0 version.

I have changed my version to Node.js v14.0.0( for example command : nvm install v14.0.0) and and fixed issue

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

4 participants