feat: upgrading angular to latest version (#266)

.circleci/config.yml

@@ -1,8 +1,11 @@
-version: 2
+version: 2.1
 
 docker_defaults: &docker_defaults
   docker:
-    - image: circleci/node:12.16.2-browsers
+    - image: cimg/node:14.20.0-browsers
+      environment:
+        NG_CLI_ANALYTICS: false
+
   working_directory: ~/project/repo
 
 attach_workspace: &attach_workspace
@@ -43,9 +46,14 @@ workflows:
       - bundle_size:
           requires:
             - build
+      - build_ssr:
+          requires:
+            - build
       # - end_to_end:
       #     requires:
       #         - build
+orbs:
+  browser-tools: circleci/browser-tools@1.4.0
 jobs:
   build:
     <<: *docker_defaults
@@ -54,21 +62,35 @@ jobs:
     <<: *docker_defaults
     steps:
       - *attach_workspace
+      - browser-tools/install-chrome
       - run:
           name: Running unit tests
           command: |
-            sudo npm test
-            sudo npm run coveralls
+            npm run lint
+            npm test
+          environment:
+            CHROME_BIN: /usr/bin/google-chrome
+  # To be added back in later
+  # sudo npm run coveralls
+  build_ssr:
+    <<: *docker_defaults
+    steps:
+      - *attach_workspace
+      - run:
+          name: Building for Angular Universal
+          command: |
+            npm rebuild
+            npm run build:ssr
   bundle_size:
     <<: *docker_defaults
     steps:
       - *attach_workspace
       - run:
           name: Checking bundle size
           command: |
-            sudo NG_CLI_ANALYTICS="false" npm rebuild
-            sudo npm run build:pkg
-            sudo npm run bundlesize
+            npm rebuild
+            npm run build:pkg
+            npm run bundlesize
   # end_to_end:
   #     <<: *docker_defaults
   #     steps:

.eslintrc.json

@@ -0,0 +1,51 @@
+{
+  "root": true,
+  "ignorePatterns": [
+    "projects/**/*"
+  ],
+  "overrides": [
+    {
+      "files": [
+        "*.ts"
+      ],
+      "parserOptions": {
+        "project": [
+          "tsconfig.json",
+          "e2e/tsconfig.json"
+        ],
+        "createDefaultProgram": true
+      },
+      "extends": [
+        "plugin:@angular-eslint/recommended",
+        "plugin:@angular-eslint/template/process-inline-templates"
+      ],
+      "rules": {
+        "@angular-eslint/component-selector": [
+          "error",
+          {
+            "prefix": "ngx",
+            "style": "kebab-case",
+            "type": "element"
+          }
+        ],
+        "@angular-eslint/directive-selector": [
+          "error",
+          {
+            "prefix": "ngx",
+            "style": "camelCase",
+            "type": "attribute"
+          }
+        ]
+      }
+    },
+    {
+      "files": [
+        "*.html"
+      ],
+      "extends": [
+        "plugin:@angular-eslint/template/recommended"
+      ],
+      "rules": {}
+    }
+  ]
+}

.github/CODEOWNERS

@@ -0,0 +1,86 @@
+# This is a comment.
+
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+
+# the repo. Unless a later match takes precedence,
+
+# @global-owner1 and @global-owner2 will be requested for
+
+# review when someone opens a pull request.
+
+*       @willmendesneto
+
+# Order is important; the last matching pattern takes the most
+
+# precedence. When someone opens a pull request that only
+
+# modifies JS files, only @js-owner and not the global
+
+# owner(s) will be requested for a review.
+
+# *.js @js-owner #This is an inline comment.
+
+# You can also use email addresses if you prefer. They'll be
+
+# used to look up users just like we do for commit author
+
+# emails.
+
+# *.go docs@example.com
+
+# Teams can be specified as code owners as well. Teams should
+
+# be identified in the format @org/team-name. Teams must have
+
+# explicit write access to the repository. In this example,
+
+# the octocats team in the octo-org organization owns all .txt files.
+
+# *.txt @octo-org/octocats
+
+# In this example, @doctocat owns any files in the build/logs
+
+# directory at the root of the repository and any of its
+
+# subdirectories.
+
+# /build/logs/ @doctocat
+
+# The `docs/*` pattern will match files like
+
+# `docs/getting-started.md` but not further nested files like
+
+# `docs/build-app/troubleshooting.md`.
+
+# docs/\* docs@example.com
+
+# In this example, @octocat owns any file in an apps directory
+
+# anywhere in your repository.
+
+# apps/ @octocat
+
+# In this example, @doctocat owns any file in the `/docs`
+
+# directory in the root of your repository and any of its
+
+# subdirectories.
+
+# /docs/ @doctocat
+
+# In this example, any change inside the `/scripts` directory
+
+# will require approval from @doctocat or @octocat.
+
+# /scripts/ @doctocat @octocat
+
+# In this example, @octocat owns any file in the `/apps`
+
+# directory in the root of your repository except for the `/apps/github`
+
+# subdirectory, as its owners are left empty.
+
+# /apps/ @octocat
+# /apps/github

.github/ISSUE_TEMPLATE.md

@@ -1,9 +1,7 @@
 **I'm submitting a ...** (check one with "x")
 
-```
-[ ] bug report => search github for a similar issue or PR before submitting
-[ ] feature request
-```
+- [ ] bug report => search github for a similar issue or PR before submitting
+- [ ] feature request
 
 **Current behavior**
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -7,15 +7,13 @@
 
 **What kind of change does this PR introduce?** _(check one with "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:
-```
+- [ ] Bugfix
+- [ ] Feature
+- [ ] Code style update (formatting, local variables)
+- [ ] Refactoring (no functional changes, no api changes)
+- [ ] Build related changes
+- [ ] CI related changes
+- [ ] Other. Please describe:
 
 If it is a Bugfix, please describe the root cause and what could have been done to prevent it…
 
@@ -25,10 +23,8 @@ If it is a Bugfix, please describe the root cause and what could have been done
 
 **Does this PR introduce a breaking change?** _(check one with "x")_
 
-```
-[ ] Yes
-[ ] No
-```
+- [ ] Yes
+- [ ] No
 
 If this PR contains a breaking change, please describe the impact and migration
 path for existing applications: …

.gitignore

@@ -4,6 +4,7 @@
 /dist
 /tmp
 /out-tsc
+**/coverage
 # Only exists if Bazel was run
 /bazel-out
 
@@ -32,6 +33,8 @@ speed-measure-plugin.json
 .history/*
 
 # misc
+.angular
+/.angular/cache
 /.sass-cache
 /connect.lock
 /coverage

.nvmrc

@@ -1 +1 @@
-v12.16.2
+v14.20.0

.prettierignore

@@ -0,0 +1 @@
+.github/CODEOWNERS

.prettierrc

@@ -0,0 +1,19 @@
+{
+  "arrowParens": "avoid",
+  "bracketSpacing": true,
+  "jsxBracketSameLine": false,
+  "printWidth": 120,
+  "semi": true,
+  "singleQuote": true,
+  "tabWidth": 2,
+  "trailingComma": "all",
+  "useTabs": false,
+  "overrides": [
+    {
+      "files": "*.scss",
+      "options": {
+        "printWidth": 80
+      }
+    }
+  ]
+}