"webpack#ajv" not installed after update to webpack 3.1.0
See original GitHub issueDo you want to request a feature or report a bug? Report a bug.
What is the current behavior?
yarn check
results in the following error:
error "ajv" is wrong version: expected "4.11.7", got "5.2.1"
error "webpack#ajv" not installed
error Found 2 errors.
If the current behavior is a bug, please provide the steps to reproduce.
- Update to webpack 3.1.0.
- Run
yarn check
.
What is the expected behavior? No errors. If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System. Node.js version: 8.1.0 wepack version: 3.1.0
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Webpack Dependency Build Error - Package Upgrade
However, I have css-loader 3.1.0 installed and not 3.6.0 (according to my package.json file). Why is it referring to this last version? –...
Read more >Installation | webpack
This guide goes through the various methods used to install webpack. Prerequisites. Before we begin, make sure you have a fresh version of...
Read more >inspectpack - npm
An inspection tool for Webpack frontend JavaScript bundles.. Latest version: 4.7.1, last published: 2 years ago. Start using inspectpack in ...
Read more >How to use ReactJS with Webpack 4, Babel 7, and Material ...
You might not know what a new version will break in your app. As you will see, the installation of these plugins made...
Read more >Finding and fixing duplicates in webpack with Inspectpack
E.g., your bundle has code from the files lodash@3.1.0/get.js and ... "installed": Resolved packages are downloaded, but not necessarily ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It’s probably related to the package manager. I have seen the same issue… even with
ajv
by using npm@5.2.0.Great