build: upgrade to Angular v11 and switch to ng-packagr (#118)

Co-authored-by: Alan Agius <[email protected]>

Author: CaerusKaru

.circleci/config.yml

@@ -1,14 +1,21 @@
 # Cache key for CircleCI. We want to invalidate the cache whenever the npm shrinkwrap
 # changed.
-var_1: &cache_key preboot-{{ checksum "npm-shrinkwrap.json" }}
+var_1: &cache_key preboot-v1-{{ checksum "yarn.lock" }}
 # Use the CircleCI browsers image that comes with NodeJS installed
-var_2: &default_docker_image circleci/node:10.12-browsers
+var_2: &docker_image cimg/node:10.20
 
-# Settings common to each job
-var_3: &job_defaults
-  working_directory: ~/ng
-  docker:
-    - image: *default_docker_image
+# Executor Definitions
+# https://circleci.com/docs/2.0/reusing-config/#authoring-reusable-executors
+executors:
+  action-executor:
+    docker:
+      - image: *docker_image
+    working_directory: ~/ng
+
+# Workspace initially persisted by the `setup` job.
+# https://circleci.com/docs/2.0/workflows/#using-workspaces-to-share-data-among-jobs
+# https://circleci.com/blog/deep-diving-into-circleci-workspaces/
+var_3: &workspace_location .
 
 # Job step for checking out the source code from GitHub. This also ensures that the source code
 # is rebased on top of master.
@@ -30,7 +37,7 @@ var_6: &save_cache
   save_cache:
     key: *cache_key
     paths:
-      - "node_modules"
+      - ~/.cache/yarn
 
 # Job step that ensures that the node module dependencies are installed and up-to-date. We use
 # Yarn with the frozen lockfile option in order to make sure that lock file and package.json are
@@ -43,58 +50,54 @@ var_7: &yarn_install
 # https://circleci.com/docs/2.0/workflows/#using-workspaces-to-share-data-among-jobs
 var_8: &attach_release_output
   attach_workspace:
-    at: dist/
+    at: *workspace_location
+
 
 
 # -----------------------------
 # Container version of CircleCI
 # -----------------------------
-version: 2
+version: 2.1
+
+orbs:
+  browser-tools: circleci/[email protected]
 
 # -----------------------------------------------------------------------------------------
 # Job definitions. Jobs which are defined just here, will not run automatically. Each job
 # must be part of a workflow definition in order to run for PRs and push builds.
 # -----------------------------------------------------------------------------------------
 jobs:
 
-  build:
-    <<: *job_defaults
+  build_and_test:
+    executor: action-executor
     steps:
       - *checkout_code
       - *restore_cache
       - *yarn_install
 
-      - run: npm run build
+      - run: yarn build
+
+      - browser-tools/install-chrome
+      - run: yarn test:once
 
       # Store the release output in the workspace storage. This means that other jobs
       # in the same workflow can attach the release output to their job.
       - persist_to_workspace:
-          root: dist
+          root: *workspace_location
           paths:
-            - "*"
-            - "**/*"
-
-      - *save_cache
-
-  test:
-    <<: *job_defaults
-    steps:
-      - *checkout_code
-      - *restore_cache
-      - *yarn_install
-
-      - run: npm run test:once
+            - ./dist
 
       - *save_cache
 
   e2e:
-    <<: *job_defaults
+    executor: action-executor
     steps:
+      - browser-tools/install-chrome
       - *checkout_code
       - *restore_cache
       - *attach_release_output
 
-      - run: npm run e2e
+      - run: yarn e2e
 
       - *save_cache
 
@@ -107,8 +110,7 @@ workflows:
 
   build_and_test:
     jobs:
-      - build
-      - test
+      - build_and_test
       - e2e:
           requires:
-            - build
+            - build_and_test

.gitignore

@@ -6,9 +6,10 @@ logs
 .DS_Store
 **/.DS_Store
 
-package-lock.json
+/npm-shrinkwrap.json
 
 dist/
+dist-tarball/
 node_modules/
 out-tsc/
 debug.log