use local lerna if global lerna used as entry point

[cdaringe]

hi all,

would you accept a PR that uses the local version of lerna (if found) when the global lerna is the cmd entry point?

Expected Behavior

• allow global lerna to use local lerna if it exists
  • allow lerna <cmd> to work vs ./node_modules/.bin/lerna <cmd>

examples:

• https://github.com/webpack/webpack/blob/master/bin/webpack.js#L10

Current Behavior

no such functionality exists, ref

[evocateur]

I'm a little confused why you would need this, if you already have lerna globally available?

[cdaringe]

Different projects, different lerna versions. Iirc some lerna versions make sure that the running version matches that listed in the lerna.json. peace of mind that the version that is running is always what is declared regardless of what shenanigans I'm doing globally. I've always loved that feature of webpack

[evocateur]

I've found calling lerna from root package.json scripts to be more than sufficient for isolating a particular version. #694 makes the version check only complain about insufficient semver (usually major version mismatch or older lerna attempting to work on "newer" repo).

For example, run lerna bootstrap in the postinstall lifecycle, and you only need to run npm install (or yarn, if you're fancy) and it will always call the local lerna:

  "name": "my-lerna-monorepo",
  "private": true,
  "scripts": {
    "postinstall": "lerna bootstrap",
    "test": "lerna run test"
  },
  devDependencies: {
    "lerna": "^2.0.0-rc.0"
  }
}

[hzoo]

yeah same request was made to Babel babel/babel#5091

[evocateur]

Closing this as a duplicate of #138

[lock]

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.