chore(): bump release

nestjs · Dec 19, 2019 · 05d2ff2 · 05d2ff2
1 parent bdbba90
commit 05d2ff2
Show file tree

Hide file tree

Showing 29 changed files with 267 additions and 4,712 deletions.
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -0,0 +1,62 @@
+version: 2
+
+aliases:
+  - &restore-cache
+    restore_cache:
+        key: dependency-cache-{{ checksum "package.json" }}
+  - &install-deps
+    run:
+        name: Install dependencies
+        command: npm ci
+  - &build-packages
+    run:
+        name: Build
+        command: npm run build
+  - &run-unit-tests
+    run:
+        name: Test
+        command: npm run test
+
+jobs:
+  build:
+    working_directory: ~/nest
+    docker:
+      - image: circleci/node:12
+    steps:
+      - checkout
+      - run:
+          name: Update NPM version
+          command: 'sudo npm install -g npm@latest'
+      - restore_cache:
+          key: dependency-cache-{{ checksum "package.json" }}
+      - run:
+          name: Install dependencies
+          command: npm ci
+      - save_cache:
+          key: dependency-cache-{{ checksum "package.json" }}
+          paths:
+            - ./node_modules
+      - run:
+          name: Build
+          command: npm run build    
+
+  unit_tests:
+    working_directory: ~/nest
+    docker:
+      - image: circleci/node:12
+    steps:
+      - checkout
+      - *restore-cache
+      - *install-deps
+      - *build-packages
+      - *run-unit-tests
+
+workflows:
+  version: 2
+  build-and-test:
+    jobs:
+      - build
+      - unit_tests:
+          requires:
+            - build
+
diff --git a/.dockerignore b/.dockerignore
diff --git a/.npmignore b/.npmignore
@@ -3,10 +3,14 @@
 .prettierrc
 .travis.yml
 Makefile
+node_modules/
+.DS_Store
+CONTRIBUTE.md
 
 # source
 **/*.ts
 *.ts
+/test
 
 # definitions
 !**/*.d.ts
@@ -15,8 +19,11 @@ Makefile
 # configuration
 renovate.json
 gulpfile.js
+tsconfig.json
+tslint.json
+tools
+/test/jest-config.json
 /.vscode
 
-
 # sample
 /sample
diff --git a/.travis.yml b/.travis.yml
diff --git a/CONTRIBUTE.md b/CONTRIBUTE.md
@@ -1,36 +1,41 @@
-# Contributing to NesjsCLI
+# Contributing to Nest CLI
+
 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 :
- - [Question or Problem?](#question)
- - [Issues and Bugs](#issue)
- - [Feature Requests](#feature)
- - [Submission Guidelines](#submit)
+
+- [Question or Problem?](#question)
+- [Issues and Bugs](#issue)
+- [Feature Requests](#feature)
+- [Submission Guidelines](#submit)
 
 ## <a name="question"></a> Got a Question or Problem ?
+
 **Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests.** You've got much better chances of getting your question answered on Stack Overflow where the questions should be tagged with tag nestjs.
 
 [Stack Overflow](https://stackoverflow.com/questions/tagged/nestjs) is a much better place to ask questions since:
 
- - 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](https://gitter.im/nestjs/nest-cli) channel.
 
 ## <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). 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".
-* **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
+- 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".
+- **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
 
 ## <a name="submit"></a> Submission Guidelines
 
@@ -40,14 +45,15 @@ 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-CLI used (```nest info```)
+- version of NestJS-CLI used (`nest info`)
 - and most importantly - a use-case that fails
 
 Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you we are going to close an issue that don't have enough info to be reproduced.
 
 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.
@@ -56,22 +62,26 @@ Before you submit your Pull Request (PR) consider the following guidelines:
 1. Create your patch, **including appropriate test cases**.
 1. Commit your changes using a descriptive commit message
 
-     ```shell
-     git commit -am "<message>"
-     ```
-    Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
+   ```shell
+   git commit -am "<message>"
+   ```
+
+   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
-    ```
-    Note: you can use -u to set your branch in upstream and just push for the next times.
+   ```shell
+   git push origin my-fix-branch
+   ```
+
+   Note: you can use -u to set your branch in upstream and just push for the next times.
 
 1. In GitHub, send a pull request to `nestjs/nest-cli:master`.
-* If we suggest changes then:
-  * Make the required updates.
-  * Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
+
+- If we suggest changes then:
+
+  - Make the required updates.
+  - Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
 
     ```shell
     git rebase master -i
@@ -85,26 +95,26 @@ That's it! Thank you for your contribution!
 After your pull request is merged, you can safely delete your branch and pull the changes
 from the main (upstream) repository:
 
-* Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
+- 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:
+- Check out the master branch:
 
-    ```shell
-    git checkout master -f
-    ```
+  ```shell
+  git checkout master -f
+  ```
 
-* Delete the local branch:
+- 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:
+- Update your master with the latest upstream version:
 
-    ```shell
-    git pull --ff upstream master
-    ```
+  ```shell
+  git pull --ff upstream master
+  ```
diff --git a/Dockerfile b/Dockerfile
diff --git a/Makefile b/Makefile