Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
6.0.0 and 7.0.0 are published on npm
See original GitHub issueIssue Description
npm has versions 6.0.0 and 7.0.0 of sequelize even though those are not valid releases yet:
https://www.npmjs.com/package/sequelize/v/6.0.0 https://www.npmjs.com/package/sequelize/v/7.0.0
Someone ran into an issue where running npm audit fix “upgraded” them to 6.0.0, which as far as I can tell, is not actually a valid release right now.
I was able to reproduce this by creating a new directory and then running npm init -y; npm i -E sequelize@4.28.8; npm audit fix --force inside it. After following those steps you will end up with sequelize@6.0.0 installed.
Is this issue dialect-specific?
- No. This issue is relevant to Sequelize as a whole.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Are there any updates on this?
I have been using 6.0.0 for a while now, but npm started complaining today that it’s unable to find it. I also can’t find it in npm version history, but it’s available in https://registry.npmjs.org/sequelize/-/sequelize-6.0.0.tgz.
@batrudinych remove sequelize from package.json file and save the file. now run the following command npm install sequelize.