build: refactor packages structure, remove bundle

[kamilmysliwiec]

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
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the new behavior?

An alternative proposal to #1060

• public API remains the same
• no breaking changes, 3rd-party packages aren't broken
• bundle directory no longer exists
• npm run build builds all packages and puts output files near to ts files
• npm run prepare fixed
• npm run build:lib builds all packages and put them into node_modules/sample/integration dirs
• no errors with npm run build
• npm run clean removes all d.ts and .js files from packages
• NPM ignores source code when publishing (.ts)
• GIT ignores bundle files (.d.ts and .js)

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[coveralls]

Coverage increased (+0.05%) to 93.743% when pulling 72616cc on build/refactor into 656ecf8 on master.

[coveralls]

Pull Request Test Coverage Report for Build 1149

• 11 of 12 (91.67%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.03%) to 93.666%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
packages/microservices/server/server-tcp.ts	3	4	75.0%

Totals
Change from base Build 1123:	-0.03%
Covered Lines:	2680
Relevant Lines:	2802

---

💛 - Coveralls

[BrunnerLivio]

Great job! This will be a huge step forward. Finally easy to overlook PRs in the future :)

General question:
Will this be a replacement of #1060, or will #1060 be implemented later on?

[BrunnerLivio]

Why do tests needed to be updated?

[kamilmysliwiec]

there was something wrong with it (probably cache dir name heh)

[kamilmysliwiec]

I think that it should be enough since it solves 99% problems already

[BrunnerLivio]

@kamilmysliwiec yes I think so too. Yarn workspaces would be cleaner, because how it handles its dependencies, but it is fine as long there is no urgent need for it.

[kamilmysliwiec]

Fully agree @BrunnerLivio

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