Monorepo fix

[daniloraisi]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

When working on a Monorepo Function files are generated per app basis, but nest build will generate everything into dist folder. So we have problems publishing them.

Issue Number: #265

What is the new behavior?

Now we are able to install Azure Functions on a project basis, but have only one entry point at root directory.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

[Jefiozie]

Great work @daniloraisi, I think this is a better solution then I've implemented it. The only confusion I have is with the folder per project in the root that contains the "azure setup". However, I don't see any other solution atm if you want to publish azure func. from the root directory.

@kamilmysliwiec could you do a review? As I said above I think this is a better a friendlier solution because you do everything from the root dir.

[kamilmysliwiec]

I'll look into this as soon as possible. Thanks for your contribution @daniloraisi!

[daniloraisi]

@Jefiozie It's a little bit confusing, but the reason to do that is that Functions will look up for a host.json file at the directory you're running the command. With this in mind, it look up for functions.json files in each subdirectory, but only 1 depth.

[daniloraisi]

Hi @kamilmysliwiec, some news about this?