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

yarn check after a fresh yarn install reports errors #6084

Open
wereHamster opened this issue Jul 11, 2018 · 0 comments
Open

yarn check after a fresh yarn install reports errors #6084

wereHamster opened this issue Jul 11, 2018 · 0 comments
Assignees
Labels

Comments

@wereHamster
Copy link

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

I have a project where yarn check reports errors and warnings after a clean yarn install.

If the current behavior is a bug, please provide the steps to reproduce.

Below is a package.json. Put it in an empty directory, then run yarn install followed by yarn check.

{
  "name": "yarn-check-after-install-errors",
  "version": "1.0.0",
  "dependencies": {
    "@types/d3-array": "^1.2.1",
    "@types/d3-collection": "^1.0.7",
    "@types/d3-dsv": "^1.0.33",
    "@types/d3-scale": "^2.0.1",
    "@types/d3-shape": "^1.2.3",
    "@types/node": "^10.3.5",
    "@types/ramda": "^0.25.34",
    "@types/react": "^16.4.1",
    "@zeit/next-css": "^0.2.0",
    "@zeit/next-typescript": "^1.1.0",
    "babel-polyfill": "^6.23.0",
    "basic-auth": "^2.0.0",
    "catalog": "^3.5.4",
    "cron": "^1.3.0",
    "d3-array": "^1.2.0",
    "d3-collection": "^1.0.3",
    "d3-dsv": "^1.0.5",
    "d3-sankey": "^0.7.1",
    "d3-scale": "^2.1.0",
    "d3-shape": "^1.2.0",
    "dotenv": "^6.0.0",
    "downshift": "^2.0.10",
    "emotion": "^9.2.4",
    "emotion-server": "^9.2.4",
    "express": "^4.16.3",
    "fast-xml-parser": "^3.11.1",
    "file-loader": "^1.1.11",
    "full-icu": "^1.2.1",
    "htpasswd": "^2.4.0",
    "http-proxy-middleware": "^0.18.0",
    "influx": "^5.0.7",
    "next": "^6.1.1",
    "node-fetch": "^2.1.2",
    "popmotion": "^8.3.3",
    "querystring": "^0.2.0",
    "ramda": "^0.25.0",
    "raw-loader": "^0.5.1",
    "react": "^16.4.1",
    "react-container-dimensions": "^1.3.4",
    "react-dom": "^16.4.1",
    "react-emotion": "^9.2.4",
    "react-select": "^1.0.0-rc.3",
    "tslint": "^5.10.0",
    "tslint-config-prettier": "^1.13.0",
    "tslint-config-standard": "^7.1.0",
    "typescript": "^2.9.2",
    "url-loader": "^1.0.1"
  }
}

An excerpt from the output:

yarn check v1.8.0
[...]
error "next#webpack" is wrong version: expected "3.10.0", got "3.12.0"
error "catalog#webpack" not installed
error "next#babel-loader" is wrong version: expected "8.0.0-beta.3", got "7.1.5"
error "catalog#babel-loader" not installed
error "catalog#html-webpack-plugin" not installed
warning "next#uglifyjs-webpack-plugin#webpack@^2.0.0 || ^3.0.0" could be deduped from "3.12.0" to "webpack@3.12.0"
warning "catalog#url-loader#file-loader@*" could be deduped from "1.1.11" to "file-loader@1.1.11"`

What is the expected behavior?

yarn check should not report any errors or warnings immediately after a clean yarn install

Please mention your node.js, yarn and operating system version.

node v10.5.0, yarn 1.8.0, macOS 10.13.5

@ghost ghost assigned rally25rs Jul 11, 2018
@ghost ghost added the triaged label Jul 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants