Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`lerna exec npm outdated` fails to resolve packages

See original GitHub issue

Expected Behavior

lerna exec npm outdated should (and used to) run npm outdated successfully in each package in the repository reporting on the outdated packages.

Current Behavior

$ npx lerna exec npm outdated 
lerna info version 2.11.0
Package             Current  Wanted  Latest  Location
redux-localstorage  MISSING   0.4.0   0.4.1  @premise/premise-core
lerna ERR! exec Errored while executing 'npm outdated' in '@premise/premise-core'
lerna ERR! execute callback with error
lerna ERR! Error: Command failed: npm outdated
lerna ERR!     at Promise.all.then.arr (/Users/craigbeck/dev/premise-frontend-v3/node_modules/lerna/node_modules/execa/index.js:236:11)
lerna WARN complete Waiting for 1 child process to exit. CTRL-C to exit immediately.
{ Error: Command failed: npm outdated
    at Promise.all.then.arr (/Users/craigbeck/dev/premise-frontend-v3/node_modules/lerna/node_modules/execa/index.js:236:11)
    at process._tickCallback (internal/process/next_tick.js:178:7)
  code: 1,
  killed: false,
  stdout: null,
  stderr: null,
  failed: true,
  signal: null,
  cmd: 'npm outdated',
  timedOut: false,
  exitCode: 1 }

Possible Solution

Steps to Reproduce (for bugs)

run npx lerna exec npm outdated

lerna.json

{
  "lerna": "2.11.0",
  "hoist": true,
  "packages": [
    "packages/*",
    "packages/libs/*",
    "packages/mobile-webviews/*",
    "packages/webapps/*"
  ],
  "version": "0.0.0"
}

lerna-debug.log

0 silly input [ 'npm', 'outdated' ]
1 silly flags { _: [ 'exec' ],
1 silly flags   'reject-cycles': false,
1 silly flags   rejectCycles: false,
1 silly flags   command: 'npm',
1 silly flags   args: [ 'outdated' ] }
2 verbose rootPath /Users/craigbeck/dev/premise-frontend-v3
3 info version 2.11.0
4 silly existsSync /Users/craigbeck/dev/premise-frontend-v3/VERSION
5 silly initialize attempt
6 silly initialize success
7 silly execute attempt
8 error exec Errored while executing 'npm outdated' in '@premise/premise-core'
9 error execute callback with error
10 error Error: Command failed: npm outdated
10 error     at Promise.all.then.arr (/Users/craigbeck/dev/premise-frontend-v3/node_modules/lerna/node_modules/execa/index.js:236:11)

Context

Your Environment

Executable	Version
`lerna --version`	2.11.0
`npm --version`	6.1.0
`yarn --version`	n/a
`node --version`	10.0.0

OS	Version
macOS High Sierra	10.13.5

Issue Analytics

State:
Created 5 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

craigbeckcommented, Jul 19, 2018

hmm, it used to work

0reactions

lock[bot]commented, Apr 3, 2019

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Top Results From Across the Web

package.json - npm Docs

Trying to install another plugin with a conflicting requirement may cause an error if the tree cannot be resolved correctly. For this reason,...

npm ci can only install packages with an ... - Stack Overflow

After a lot of research, I was able to figure out that this happens when you are not using npm install for installing...

unable to resolve dependency tree npm - You.com | The search ...

Unable to resolve dependency tree error when installing npm packages ... 1.79 s [16:22:51] Error: Command failed: lerna exec -- npm install blockly@beta...

Things I wish I had known when I started JavaScript monorepo ...

We no longer need to run complicated Lerna commands to add new dependency to a specific package, we just use plain old npm...

@lerna/run | Yarn - Package Manager

@lerna/run ... Run an npm script in each package that contains that script. lerna ... core: more detailed error message when version cannot...