lerna init should add lerna as a devDependency

[hzoo]

I think we want this as a devDep right? Also do we want to add ^ in front as well?

Also, this means we don't want users to use it as a global npm package?

cc @thejameskyle

[jamiebuilds]

How does ^ interact with x.x.x-beta.x?

And my plan in the future is to make the global CLI use the local version if it exists which would be the preferred way.

[hzoo]

If you do ^x.x.x-beta it should update all betas and more. http://semver.npmjs.com/

It would also get 2.0.1 and 2.1.0 if released

[jamiebuilds]

I don't know about the carrot range because I want the version in lerna.json to always match the version in devDependencies. We can either lock it down to the specific version or open them both up using semver.satisfies. What do you think?

[jamiebuilds]

I'm going to merge this as is for now

[hzoo]

Ok lets go with locking it down atm then and reevaluate ^ later. Similar to flowconfig although in that case if you don't specify a version it allows any version and otherwise errors if it doesn't match

[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.