Yarn outdated doesn't show outdated packages.

kickthedragon commented 5 years ago

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

Bug

What is the current behavior? Does not print outdated packages, only shows warnings

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

I've narrowed it down to either upgrading to node version 10.2.0, or declaring resolutions in the package.json since those were the only two changes.

What is the expected behavior? yarn outdated prints the correct outdated packages (specifically angular should detect 1.7.4 at the time of this post)

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

Node 10.2.0 yarn 1.10.1 MacOS 10.14.1

Below is an attached package.json with all the packages in the project. It should correctly detect angular 1.7.4 at the time of this post.

{
  "name": "com.yarn.outdated",
  "version": "0.0.1",
  "productName": "Yarn outdated fails",
  "description": "yarn outdated fails",
  "private": true,
  "scripts": {
    "dev": "electron-webpack dev",
    "compile": "electron-webpack",
    "rebuild-deps": "electron-builder install-app-deps",
    "preinstall": "node install_dependencies.js",
    "build": "yarn dist",
    "dist": "yarn compile && electron-builder",
    "pub": "yarn compile && electron-builder --publish always",
    "dist:dir": "yarn dist --dir -c.compression=store -c.mac.identity=null"
  },
  "dependencies": {
    "@uirouter/angularjs": "^1.0.19",
    "amazon-cognito-auth-js": "^1.2.4",
    "angular": "~1.7.2",
    "angular-animate": "~1.7.2",
    "angular-aria": "~1.7.2",
    "angular-resource": "~1.7.2",
    "angular-sanitize": "~1.7.2",
    "dmg": "^0.1.0",
    "electron-context-menu": "^0.10.0",
    "electron-google-analytics": "~0.1.0",
    "electron-localshortcut": "^3.1.0",
    "electron-log": "^2.2.17",
    "electron-online": "^1.0.0",
    "electron-platform": "^1.2.0",
    "electron-prompt": "^1.2.0",
    "electron-store": "^2.0.0",
    "electron-unhandled": "^1.1.0",
    "electron-updater": "^3.1.2",
    "fs-extra": "^7.0.0",
    "is-online": "^7.0.0",
    "jquery": "^3.3.1",
    "lodash": "^4.17.11",
    "melanke-watchjs": "^1.5.0",
    "plist": "^3.0.1",
    "request": "^2.88.0",
    "semver": "^5.6.0",
    "speedometer": "^1.1.0",
    "webtorrent": "^0.102.4",
    "yauzl": "^2.10.0"
  },
  "devDependencies": {
    "angular2-template-loader": "^0.6.2",
    "babel-eslint": "^10.0.1",
    "babel-plugin-angularjs-annotate": "^0.9.0",
    "electron": "^3.0.5",
    "electron-builder": "20.28.4",
    "electron-context-menu": "^0.9.1",
    "electron-publisher-s3": "^20.17.2",
    "electron-webpack": "^2.3.1",
    "eslint": "^5.7.0",
    "extract-loader": "^3.0.0",
    "file-loader": "^2.0.0",
    "html-loader": "^0.5.5",
    "json-loader": "^0.5.7",
    "node-sass": "^4.9.4",
    "raw-loader": "^0.5.1",
    "sass-loader": "^7.1.0",
    "webpack": "^4.22.0"
  },
  "resolutions": {
    "upath": "^1.0.5",
    "bufferutil": "^4.0.0"
  },
  "engines": {
    "node": "~10.2.0",
    "yarn": "^1.10.1"
  }
}

evanhammer commented 5 years ago

I'm seeing this too

ThomasdenH commented 5 years ago

Unlike npm, yarn does not update the package.json, just the lock file. So maybe you have the most recent version installed?

yarnpkg / yarn

Yarn outdated doesn't show outdated packages. #6570