Nest-cli: Monorepo for backend

[bovandersteene]

I'm submitting a...

[ ] Regression 
[ ] Bug report
[ X ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

If you generate a project now, you have only one root source

Expected behavior

You can add multiple project to one project root, simulair to ng-packager that works together with angular-cli. If you have a set of microservices you can pacakage them together and create a BFF without having any issues on versioning

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

[BrunnerLivio]

I am not quite sure whether NestJS should support this out of the box, since this use case is quite specific to the project.

I am using a monorepo for my Nest project and I use this repository as reference if that helps.

[bovandersteene]

But then you don't generate the controllers, pipes, services, ... with the CLI? Like I prefer

[kamilmysliwiec]

Why not @bovandersteene?

[kamilmysliwiec]

I'm working on nest g lib support just FYI

[MarkPieszak]

Just incase others find this thread.

We have announced official Monorepo support (full article) to create additional Applications or Libraries all within a single monorepo workspace.