feat(core) allow the NestModule.configure() method to be async

[zailic]

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?

[ ] Bugfix
[x] 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?

Issue Number: #1384

What is the new behavior?

Allows the NestModule.configure() method to be asynchronous. More details can be found on #1384.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[coveralls]

Pull Request Test Coverage Report for Build 4264

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 95.236%

---

Totals
Change from base Build 4098:	0.0%
Covered Lines:	3638
Relevant Lines:	3820

---

💛 - Coveralls

[kamilmysliwiec]

I think that we can just remove the return type here entirely.

[zailic]

I think you're absolutely right.

[kamilmysliwiec]

Could you rebase your PR to the latest changes on master? It seems that it contains lots of renovate commits now:)

[zailic]

ups... sorry about that! I'll do it right now.

[zailic]

The header of this issue is a lie:). I don't want to merge 54 commits... Bellow are the changes for CR:
master...zailic:IonutZailic-IssueNo1384

[kamilmysliwiec]

Thanks!

[zailic]

Thank you! Can't wait for 6.6.0 release:)

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