{"action":"opened","issue":{"url":"https://api.github.com/repos/lerna/lerna/issues/1501","repository_url":"https://api.github.com/repos/lerna/lerna","labels_url":"https://api.github.com/repos/lerna/lerna/issues/1501/labels{/name}","comments_url":"https://api.github.com/repos/lerna/lerna/issues/1501/comments","events_url":"https://api.github.com/repos/lerna/lerna/issues/1501/events","html_url":"https://github.com/lerna/lerna/issues/1501","id":341555041,"node_id":"MDU6SXNzdWUzNDE1NTUwNDE=","number":1501,"title":"How to check for outdated dependencies in packages.","user":{"login":"hannadrehman","id":23405869,"node_id":"MDQ6VXNlcjIzNDA1ODY5","avatar_url":"https://avatars3.githubusercontent.com/u/23405869?v=4","gravatar_id":"","url":"https://api.github.com/users/hannadrehman","html_url":"https://github.com/hannadrehman","followers_url":"https://api.github.com/users/hannadrehman/followers","following_url":"https://api.github.com/users/hannadrehman/following{/other_user}","gists_url":"https://api.github.com/users/hannadrehman/gists{/gist_id}","starred_url":"https://api.github.com/users/hannadrehman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hannadrehman/subscriptions","organizations_url":"https://api.github.com/users/hannadrehman/orgs","repos_url":"https://api.github.com/users/hannadrehman/repos","events_url":"https://api.github.com/users/hannadrehman/events{/privacy}","received_events_url":"https://api.github.com/users/hannadrehman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-16T14:58:58Z","updated_at":"2018-07-16T14:58:58Z","closed_at":null,"author_association":"NONE","body":"<!--- Provide a general summary of the issue in the Title above -->\r\nI am trying to convert our existing projects into a Lerna project. so I have created all packages for different repositories and setup all tools and config for my project. everything is working fine. \r\n\r\nI want to know how to list all dependencies in my packages that are outdated. I wish to keep my project up to date with all new updates.\r\n## Expected Behavior\r\nI want to run `npm outdated` or any lerna command which lists all dependencies that have changed/updated.\r\n\r\n## Current Behavior\r\nwhen i run `npm outdated` or `lerna exec npm outdated` in my local package it obviously fails because i am using local packages which is not there in npm repo .. (react-elements-md is my local package) \r\n```\r\nnpm ERR! code E404\r\nnpm ERR! 404 Not found : react-elements-md\r\nnpm ERR! 404 \r\nnpm ERR! 404  'react-elements-md' is not in the npm registry.\r\nnpm ERR! 404 You should bug the author to publish it (or use the name yourself!)\r\nnpm ERR! 404 \r\nnpm ERR! 404 Note that you can also install from a\r\nnpm ERR! 404 tarball, folder, http url, or git url.\r\n\r\nnpm ERR! A complete log of this run can be found in:\r\nnpm ERR!     /Users/akashtalreja/.npm/_logs/2018-07-16T14_43_51_022Z-debug.log\r\nlerna ERR! exec Errored while executing 'npm outdated' in 'react-redux-sagas'\r\nlerna ERR! execute callback with error\r\nlerna ERR! Error: Command failed: npm outdated\r\nlerna ERR!     at Promise.all.then.arr (/usr/local/lib/node_modules/lerna/node_modules/execa/index.js:236:11)\r\nlerna ERR!     at <anonymous>\r\n{ Error: Command failed: npm outdated\r\n    at Promise.all.then.arr (/usr/local/lib/node_modules/lerna/node_modules/execa/index.js:236:11)\r\n    at <anonymous>\r\n    at process._tickCallback (internal/process/next_tick.js:160:7)\r\n  code: 1,\r\n  killed: false,\r\n  stdout: null,\r\n  stderr: null,\r\n  failed: true,\r\n  signal: null,\r\n  cmd: 'npm outdated',\r\n  timedOut: false,\r\n  exitCode: 1 }\r\n```\r\n## Possible Solution\r\npossible solution i can think of some command like `lerna outdated` which would list down the dependencies in a packages that can updated.\r\n\r\n## Steps to Reproduce (for bugs)\r\nhit `npm outdated` in any package that used your local repository\r\n<details><summary>lerna.json</summary><p>\r\n<!-- browsers demand the next line be empty -->\r\n\r\n```json\r\n<!-- Please paste your `lerna.json` here -->\r\n```\r\n</p></details>\r\n\r\n<details>\r\n<summary>\r\n  am i missing something ? it looks quite simple there must be a way to update npm dependencies. and keep your project updated. i also read in some issue @evocateur mentioning \r\n\"If you're never publishing packages to a registry (public or private), I\r\ndon't recommend using lerna. There is no shame in relative path imports.\" .\r\n. since i am not going to publish anyway, should i really use lerna in my project ?\r\n</summary>\r\n<p>\r\n\r\n</p></details>\r\n\r\n\r\n| Executable | Version |\r\n| ---: | :--- |\r\n| `lerna --version` | 2.11.0 |\r\n| `npm --version`  | 6.2.0 |\r\n| `yarn --version` | 1.6.0 |\r\n| `node --version` | 9.6.1 |\r\n\r\n| OS | Version |\r\n|  macOS High Sierra | 10.13.3-= |\r\n| NAME | VERSION |\r\n\r\n"}}
{"actor":{"display_login":"hannadrehman"}}