cypress-io/cypress-react-unit-test

Warnings during yarn install (Yarn 2)

Closed this issue · 1 comments

larrifax commented

I'm using Yarn 2 to install packages in my app that depends on cypress-react-unit-test. When installing, yarn spits out these log messages:

➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide @babel/core@^7.0.0-0 requested by @babel/plugin-transform-modules-commonjs@npm:7.10.4
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide cypress@* requested by @cypress/code-coverage@npm:3.8.1
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide @babel/core@^7.0.1 requested by @cypress/webpack-preprocessor@npm:5.4.5
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide @babel/preset-env@^7.0.0 requested by @cypress/webpack-preprocessor@npm:5.4.5
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide babel-loader@^8.0.2 requested by @cypress/webpack-preprocessor@npm:5.4.5
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide webpack@^4.18.1 requested by @cypress/webpack-preprocessor@npm:5.4.5
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide node-sass@^4.7.2 requested by @zeit/next-sass@npm:1.0.1
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide react-dom@^16.8 requested by framer-motion@npm:2.6.13
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide react@^16.8 requested by framer-motion@npm:2.6.13
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide react-dom@^16.6.0 requested by next@npm:9.5.3
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide react@^16.6.0 requested by next@npm:9.5.3
➤ YN0002: │ cypress-react-unit-test@npm:4.14.1 doesn't provide react@>= 16.8.0 requested by react-i18next@npm:11.7.2

I see a couple of issues here:

  1. There seems to be a lot of dependencies in package.json that aren't needed in order to consume the library. E.g. next, react-i18next, etc. These should probably be moved to devDependencies.
  2. cypress should probably be specified as a peerDependency.
  3. The dependencies that are needed should have their peerDependencies added to either dependencies or peerDependencies.
bahmutov commented

🎉 This issue has been resolved in version 4.14.3 🎉

The release is available on:

Your semantic-release bot 📦🚀