build: refactor packages structure, remove bundle

.gitignore

@@ -6,16 +6,18 @@ node_modules/
 /.awcache
 /.vscode
 
+# bundle
+packages/**/*.d.ts
+packages/**/*.js
+
 # misc
 .DS_Store
 lerna-debug.log
 npm-debug.log
 yarn-error.log
-/src/common/npm-debug.log
-/src/core/npm-debug.log
-/src/testing/npm-debug.log
-/src/microservices/npm-debug.log
-/src/websockets/npm-debug.log
+/**/npm-debug.log
+/packages/**/.npmignore
+/packages/**/LICENSE
 
 # example
 /quick-start

.npmignore

@@ -0,0 +1,9 @@
+# source
+**/*.ts
+*.ts
+
+# configuration
+package-lock.json
+tslint.json
+tsconfig.json
+.prettierrc

.prettierignore

@@ -1 +1,2 @@
-/bundle
+packages/**/*.d.ts
+packages/**/*.js

.travis.yml

@@ -17,7 +17,7 @@ before_install:
   - npm i -g npm@latest
 install:
   - npm ci
-  - gulp build
+  - npm run build:dev
 script:
   - npm run lint
   - npm test

CONTRIBUTING.md

@@ -3,15 +3,15 @@
 We would love for you to contribute to Nest and help make it even better than it is
 today! As a contributor, here are the guidelines we would like you to follow:
 
- - [Code of Conduct](#coc)
- - [Question or Problem?](#question)
- - [Issues and Bugs](#issue)
- - [Feature Requests](#feature)
- - [Submission Guidelines](#submit)
- - [Development Setup](#development)
- - [Coding Rules](#rules)
- - [Commit Message Guidelines](#commit)
- <!-- - [Signing the CLA](#cla) -->
+* [Code of Conduct](#coc)
+* [Question or Problem?](#question)
+* [Issues and Bugs](#issue)
+* [Feature Requests](#feature)
+* [Submission Guidelines](#submit)
+* [Development Setup](#development)
+* [Coding Rules](#rules)
+* [Commit Message Guidelines](#commit)
+  <!-- - [Signing the CLA](#cla) -->
 
 <!-- ## <a name="coc"></a> Code of Conduct
 Help us keep Nest open and inclusive. Please read and follow our [Code of Conduct][coc]. -->
@@ -23,27 +23,30 @@ Help us keep Nest open and inclusive. Please read and follow our [Code of Conduc
 Stack Overflow is a much better place to ask questions since:
 
 <!-- - there are thousands of people willing to help on Stack Overflow [maybe one day] -->
-- questions and answers stay available for public viewing so your question / answer might help someone else
-- Stack Overflow's voting system assures that the best answers are prominently visible.
+
+* questions and answers stay available for public viewing so your question / answer might help someone else
+* Stack Overflow's voting system assures that the best answers are prominently visible.
 
 To save your and our time, we will systematically close all issues that are requests for general support and redirect people to Stack Overflow.
 
 If you would like to chat about the question in real-time, you can reach out via [our gitter channel][gitter].
 
 ## <a name="issue"></a> Found a Bug?
+
 If you find a bug in the source code, you can help us by
 [submitting an issue](#submit-issue) to our [GitHub Repository][github]. Even better, you can
 [submit a Pull Request](#submit-pr) with a fix.
 
 ## <a name="feature"></a> Missing a Feature?
-You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub
-Repository. If you would like to *implement* a new feature, please submit an issue with
+
+You can _request_ a new feature by [submitting an issue](#submit-issue) to our GitHub
+Repository. If you would like to _implement_ a new feature, please submit an issue with
 a proposal for your work first, to be sure that we can use it.
 Please consider what kind of change it is:
 
 * For a **Major Feature**, first open an issue and outline your proposal so that it can be
-discussed. This will also allow us to better coordinate our efforts, prevent duplication of work,
-and help you to craft the change so that it is successfully accepted into the project. For your issue name, please prefix your proposal with `[discussion]`, for example "[discussion]: your feature idea".
+  discussed. This will also allow us to better coordinate our efforts, prevent duplication of work,
+  and help you to craft the change so that it is successfully accepted into the project. For your issue name, please prefix your proposal with `[discussion]`, for example "[discussion]: your feature idea".
 * **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
 
 ## <a name="submit"></a> Submission Guidelines
@@ -54,9 +57,9 @@ Before you submit an issue, please search the issue tracker, maybe an issue for
 
 We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs we will systematically ask you to provide a minimal reproduction scenario using a repository or [Gist](https://gist.github.com/). Having a live, reproducible scenario gives us wealth of important information without going back & forth to you with additional questions like:
 
-- version of NestJS used
-- 3rd-party libraries and their versions
-- and most importantly - a use-case that fails
+* version of NestJS used
+* 3rd-party libraries and their versions
+* and most importantly - a use-case that fails
 
 <!--
 // TODO we need to create a playground, similar to plunkr
@@ -69,42 +72,45 @@ Unfortunately, we are not able to investigate / fix bugs without a minimal repro
 
 You can file new issues by filling out our [new issue form](https://github.com/nestjs/nest/issues/new).
 
-
 ### <a name="submit-pr"></a> Submitting a Pull Request (PR)
+
 Before you submit your Pull Request (PR) consider the following guidelines:
 
 1. Search [GitHub](https://github.com/nestjs/nest/pulls) for an open or closed PR
-  that relates to your submission. You don't want to duplicate effort.
-<!-- 1. Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs.
+   that relates to your submission. You don't want to duplicate effort.
+   <!-- 1. Please sign our [Contributor License Agreement (CLA)](#cla) before sending PRs.
   We cannot accept code without this. -->
 1. Fork the nestjs/nest repo.
 1. Make your changes in a new git branch:
 
-     ```shell
-     git checkout -b my-fix-branch master
-     ```
+   ```shell
+   git checkout -b my-fix-branch master
+   ```
 
 1. Create your patch, **including appropriate test cases**.
 1. Follow our [Coding Rules](#rules).
 1. Run the full Nest test suite, as described in the [developer documentation][dev-doc],
-  and ensure that all tests pass.
+   and ensure that all tests pass.
 1. Commit your changes using a descriptive commit message that follows our
-  [commit message conventions](#commit). Adherence to these conventions
-  is necessary because release notes are automatically generated from these messages.
+   [commit message conventions](#commit). Adherence to these conventions
+   is necessary because release notes are automatically generated from these messages.
 
-     ```shell
-     git commit -a
-     ```
-    Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
+   ```shell
+   git commit -a
+   ```
+
+   Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
 
 1. Push your branch to GitHub:
 
-    ```shell
-    git push origin my-fix-branch
-    ```
+   ```shell
+   git push origin my-fix-branch
+   ```
 
 1. In GitHub, send a pull request to `nestjs:master`.
+
 * If we suggest changes then:
+
   * Make the required updates.
   * Re-run the Nest test suites to ensure tests are still passing.
   * Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
@@ -123,38 +129,40 @@ from the main (upstream) repository:
 
 * Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
 
-    ```shell
-    git push origin --delete my-fix-branch
-    ```
+  ```shell
+  git push origin --delete my-fix-branch
+  ```
 
 * Check out the master branch:
 
-    ```shell
-    git checkout master -f
-    ```
+  ```shell
+  git checkout master -f
+  ```
 
 * Delete the local branch:
 
-    ```shell
-    git branch -D my-fix-branch
-    ```
+  ```shell
+  git branch -D my-fix-branch
+  ```
 
 * Update your master with the latest upstream version:
 
-    ```shell
-    git pull --ff upstream master
-    ```
-    
+  ```shell
+  git pull --ff upstream master
+  ```
+
 ## <a name="development"></a> Development Setup
 
 You will need Node.js version 8.9.0+.
 
 1. After cloning the repo, run:
+
 ```bash
 $ npm i # (or yarn install)
 ```
 
 2. In order to prepare your environment run `prepare.sh` shell script:
+
 ```bash
 $ sh scripts/prepare.sh
 ```
@@ -164,10 +172,13 @@ That will compile fresh packages and afterward, move them to all `sample` direct
 ### Commonly used NPM scripts
 
 ```bash
+# build all packages and put them near to their source .ts files
+$ npm run build
+
 # build all packages and move to "sample" and "integration" directories
 # if cross-packages breaking changes were performed you may face irrelevant errors
 # in order to verify the build, you can run this command again then
-$ npm run build
+$ npm run build:dev
 
 # run the full unit tests suite
 $ npm run test
@@ -181,10 +192,11 @@ $ npm run lint
 ```
 
 ## <a name="rules"></a> Coding Rules
+
 To ensure consistency throughout the source code, keep these rules in mind as you are working:
 
 * All features or bug fixes **must be tested** by one or more specs (unit-tests).
-<!--
+  <!--
 // We're working on auto-documentation.
 * All public API methods **must be documented**. (Details TBC). -->
 * We follow [Google's JavaScript Style Guide][js-style-guide], but wrap all code at
@@ -193,12 +205,13 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
 
 ## <a name="commit"></a> Commit Message Guidelines
 
-We have very precise rules over how our git commit messages can be formatted.  This leads to **more
-readable messages** that are easy to follow when looking through the **project history**.  But also,
+We have very precise rules over how our git commit messages can be formatted. This leads to **more
+readable messages** that are easy to follow when looking through the **project history**. But also,
 we use the git commit messages to **generate the Nest change log**.
 
 ### Commit Message Format
-Each commit message consists of a **header**, a **body** and a **footer**.  The header has a special
+
+Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
 format that includes a **type**, a **scope** and a **subject**:
 
 ```
@@ -224,9 +237,11 @@ bugfix(core) need to depend on latest rxjs and zone.js
 ```
 
 ### Revert
-If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
+
+If the commit reverts a previous commit, it should begin with `revert:`, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
 
 ### Type
+
 Must be one of the following:
 
 * **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
@@ -240,6 +255,7 @@ Must be one of the following:
 * **test**: Adding missing tests or correcting existing tests
 
 ### Scope
+
 The scope should be the name of the npm package affected (as perceived by person reading changelog generated from commit messages.
 
 The following is the list of supported scopes:
@@ -256,21 +272,24 @@ There are currently a few exceptions to the "use package name" rule:
 * **packaging**: used for changes that change the npm package layout in all of our packages, e.g. public path changes, package.json changes done to all packages, d.ts file/format changes, changes to bundles, etc.
 * **changelog**: used for updating the release notes in CHANGELOG.md
 * **sample/#**: for the example apps directory, replacing # with the example app number
-<!-- * **aio**: used for docs-app (angular.io) related changes within the /aio directory of the repo -->
+  <!-- * **aio**: used for docs-app (angular.io) related changes within the /aio directory of the repo -->
 * none/empty string: useful for `style`, `test` and `refactor` changes that are done across all packages (e.g. `style: add missing semicolons`)
 
 ### Subject
+
 The subject contains succinct description of the change:
 
 * use the imperative, present tense: "change" not "changed" nor "changes"
 * don't capitalize first letter
 * no dot (.) at the end
 
 ### Body
+
 Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
 The body should include the motivation for the change and contrast this with previous behavior.
 
 ### Footer
+
 The footer should contain any information about **Breaking Changes** and is also the place to
 reference GitHub issues that this commit **Closes**.
 
@@ -287,9 +306,10 @@ changes to be accepted, the CLA must be signed. It's a quick process, we promise
 * For corporations we'll need you to
   [print, sign and one of scan+email, fax or mail the form][corporate-cla]. -->
 
-
 <!-- [angular-group]: https://groups.google.com/forum/#!forum/angular -->
+
 <!-- [coc]: https://github.com/angular/code-of-conduct/blob/master/CODE_OF_CONDUCT.md -->
+
 [commit-message-format]: https://docs.google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#
 [corporate-cla]: http://code.google.com/legal/corporate-cla-v1.0.html
 [dev-doc]: https://github.com/nestjs/nest/blob/master/docs/DEVELOPER.md
@@ -300,4 +320,5 @@ changes to be accepted, the CLA must be signed. It's a quick process, we promise
 [jsfiddle]: http://jsfiddle.net
 [plunker]: http://plnkr.co/edit
 [runnable]: http://runnable.com
+
 <!-- [stackoverflow]: http://stackoverflow.com/questions/tagged/angular -->