Add Lerna functionality

[wbhob]

This PR will use lerna for managing the monorepo. This addresses #68. I have mapped the npm publish command to lerna publish, so there should not be much difference.

Important note: I have mapped lerna to src. I don't have a valid build command on the current repo, so change the property in lerna.json to whatever the build directory is.

[coveralls]

Coverage remained the same at 93.951% when pulling 598056a on wbhob:lerna into dc7869b on nestjs:master.

[coveralls]

Coverage remained the same at 93.951% when pulling 598056a on wbhob:lerna into dc7869b on nestjs:master.

[wbhob]

Fixed merge conflicts

[coveralls]

Coverage remained the same at 93.951% when pulling 9a04b40 on wbhob:lerna into dc7869b on nestjs:master.

[kamilmysliwiec]

Hi @wbhob,
I appreciate your work but honestly, I don't see the reason why we need an additional tool to manage only 5 repos 🙁 Lerna is great, but we don't need it since all of the repositories may have a different release number.

[wbhob]

So that’s the thing: they should all have the same release number, because they are codependent. It will get very confusing VERY fast if there are more packages or some packages have minor versions. Like angular, it’s kmportant to have every package on the same version for developer experience.

[wbhob]

@kamilmysliwiec can you see my previous comment and tell me your thoughts?

On the whole, I think it's good that we have tools like Lerna at our disposal, so we don't have to write scripts ourselves.

[MonsieurMan]

I'm on par with @wbhob, if packages come as a bundle they should definitely have the same version number even if no changes were introduced, it's going to be a hell if we have to keep track of which version works with which other.

[kamilmysliwiec]

Thanks @wbhob @MonsieurMan - you convinced me 🙂 Lerna is here now

[lock]

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