chore: update deps

.circleci/config.yml

@@ -7,8 +7,7 @@ jobs:
           JOBS: 1
     steps:
       - checkout
-      - run: sudo yarn global add @angular/cli@8
-      - run: sudo yarn global add greenkeeper-lockfile@1
+      - run: sudo yarn global add @angular/cli@10
       - restore_cache:
           keys:
           - deps-{{ .Branch }}-{{ checksum "yarn.lock" }}

.editorconfig

@@ -3,12 +3,11 @@ root = true
 
 [*]
 charset = utf-8
-end_of_line = lf
 indent_style = space
 indent_size = 2
 insert_final_newline = true
 trim_trailing_whitespace = true
 
 [*.md]
-max_line_length = 140
+max_line_length = off
 trim_trailing_whitespace = false

.eslintrc.json

@@ -0,0 +1,31 @@
+{
+  "root": true,
+  "ignorePatterns": ["**/*"],
+  "plugins": ["@nrwl/nx"],
+  "overrides": [
+    {
+      "files": ["*.ts", "*.tsx", "*.js", "*.jsx"],
+      "rules": {
+        "@nrwl/nx/enforce-module-boundaries": [
+          "error",
+          {
+            "enforceBuildableLibDependency": true,
+            "allow": [],
+            "depConstraints": [{ "sourceTag": "*", "onlyDependOnLibsWithTags": ["*"] }]
+          }
+        ]
+      }
+    },
+    {
+      "files": ["*.ts", "*.tsx"],
+      "extends": ["plugin:@nrwl/nx/typescript"],
+      "parserOptions": { "project": "./tsconfig.*?.json" },
+      "rules": {}
+    },
+    {
+      "files": ["*.js", "*.jsx"],
+      "extends": ["plugin:@nrwl/nx/javascript"],
+      "rules": {}
+    }
+  ]
+}

.github/ISSUE_TEMPLATE.md

@@ -4,7 +4,8 @@ PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATI
 ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
 -->
 
-**I'm submitting a ...**  (check one with "x")
+**I'm submitting a ...** (check one with "x")
+
 ```
 [ ] Regression (a behavior that used to work and stopped working in a new release)
 [ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
@@ -14,37 +15,44 @@ ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
 ```
 
 **Current behavior**
+
 <!-- Describe how the issue manifests. -->
 
 **Expected/desired behavior**
+
 <!-- Describe what the desired behavior would be. -->
 
 **Minimal reproduction of the problem with instructions**
+
 <!--
 For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
 https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
 -->
 
 **What is the motivation / use case for changing the behavior?**
+
 <!-- Describe the motivation or the concrete use case. -->
 
 **Environment**
-* **Angular version:** X.Y.Z
+
+- **Angular version:** X.Y.Z
 <!-- Check whether this is still an issue in the most recent Angular version -->
 
-* **Browser:**
-- [ ] Chrome (desktop) version XX
-- [ ] Chrome (Android) version XX
-- [ ] Chrome (iOS) version XX
-- [ ] Firefox version XX
-- [ ] Safari (desktop) version XX
-- [ ] Safari (iOS) version XX
-- [ ] IE version XX
-- [ ] Edge version XX
-
-* **For Tooling issues:**
-- Node version: XX  <!-- run `node --version` -->
-- Platform:  <!-- Mac, Linux, Windows -->
-
-* Others:
+- **Browser:**
+
+* [ ] Chrome (desktop) version XX
+* [ ] Chrome (Android) version XX
+* [ ] Chrome (iOS) version XX
+* [ ] Firefox version XX
+* [ ] Safari (desktop) version XX
+* [ ] Safari (iOS) version XX
+* [ ] IE version XX
+* [ ] Edge version XX
+
+- **For Tooling issues:**
+
+* Node version: XX <!-- run `node --version` -->
+* Platform: <!-- Mac, Linux, Windows -->
+
+- Others:
 <!-- Anything else relevant?  Operating system version, IDE, package manager, HTTP server, ... -->

.husky/commit-msg

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npx --no-install commitlint --edit $1

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npx --no-install lint-staged

.prettierignore

@@ -1,48 +1,4 @@
 # Add files here to ignore them from prettier formatting
 
-# compiled output
 /dist
-/tmp
-/out-tsc
-
-# dependencies
-node_modules/
-
-# IDEs and editors
-/.idea
-.project
-.classpath
-.c9/
-*.launch
-.settings/
-*.sublime-workspace
-
-# IDE - VSCode
-.vscode/*
-!.vscode/settings.json
-!.vscode/tasks.json
-!.vscode/launch.json
-!.vscode/extensions.json
-
-# misc
-/.sass-cache
-/connect.lock
 /coverage
-/libpeerconnection.log
-npm-debug.log
-yarn-error.log
-testem.log
-/typings
-
-# System Files
-.DS_Store
-Thumbs.db
-
-# others
-/.awcache
-/.cache
-/docs
-/tools
-angular.json
-test-report.xml
-yarn.lock

.prettierrc

@@ -1,4 +1,20 @@
 {
-  "printWidth": 140,
-  "singleQuote": true
+  "printWidth": 120,
+  "singleQuote": true,
+  "trailingComma": "none",
+  "arrowParens": "avoid",
+  "overrides": [
+    {
+      "files": "*.component.html",
+      "options": {
+        "parser": "angular"
+      }
+    },
+    {
+      "files": "*.html",
+      "options": {
+        "parser": "html"
+      }
+    }
+  ]
 }

CODE_OF_CONDUCT.md

@@ -8,19 +8,19 @@ In the interest of fostering an open and welcoming environment, we as contributo
 
 Examples of behavior that contributes to creating a positive environment include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Our Responsibilities
 

CONTRIBUTING.md

@@ -125,7 +125,7 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
 
 - All features or bug fixes **must be tested** by one or more specs (unit-tests).
 - All public API methods **must be documented**. (Details TBC).
-- We follow [fulls1z3's Angular TSLint rules][angular-tslint-rules].
+- We follow [eslint:recommended][eslint].
 
 ## <a name="commit"></a> Commit message guidelines
 
@@ -136,9 +136,7 @@ the `universal` change log**.
 ### Commit Message Format
 
 Each commit message consists of a **header**, a **body** and a **footer**. The header has a special format that includes
-a **type**, an _optional_ **scope** (_when applicable_) and a **subject**:
-
-#### Without scope
+a **type** and a **subject**:
 
 ```
 <type>: <subject>
@@ -148,17 +146,7 @@ a **type**, an _optional_ **scope** (_when applicable_) and a **subject**:
 <footer>
 ```
 
-#### With scope
-
-```
-<type>(<scope>): <subject>
-<BLANK LINE>
-<body>
-<BLANK LINE>
-<footer>
-```
-
-The **header** is mandatory and the **scope** of the header is optional.
+The **header** is mandatory.
 
 Any line of the commit message cannot be longer 100 characters. This allows the message to be easier to read on GitHub as
 well as in various git tools.
@@ -169,11 +157,11 @@ if any.
 Samples: (even more [samples](https://github.com/fulls1z3/universal/commits/master))
 
 ```
-docs(changelog): update change log to alpha.4
+docs: update change log to alpha.4
 ```
 
 ```
-fix(release): need to depend on latest rxjs and zone.js
+fix: need to depend on latest rxjs and zone.js
 
 The version in our package.json gets copied to the one we publish, and users need the latest of these.
 ```
@@ -187,18 +175,17 @@ In the body it should say: `This reverts commit <hash>.`, where the hash is the
 
 Must be one of the following:
 
-- **build**: Changes that affect the build system or external dependencies (example scopes: gulp, npm, webpack)
-- **ci**: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, etc)
-- **docs**: Documentation only changes
 - **feat**: A new feature
 - **fix**: A bug fix
-- **perf**: A code change that improves performance
-- **refactor**: A code change that neither fixes a bug nor adds a feature
+- **docs**: Documentation only changes
 - **style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+- **refactor**: A code change that neither fixes a bug nor adds a feature
+- **perf**: A code change that improves performance
 - **test**: Adding missing tests or correcting existing tests
-
-- **packaging**: used for changes that change the package layout (_e.g. package.json, bundles, path changes, etc._)
-- **changelog**: used for updating the release notes in CHANGELOG.md
+- **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
+- **ci**: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
+- **chore**: Other changes that don't modify src or test files
+- **revert**: Reverts a previous commit
 
 ### Subject
 
@@ -223,4 +210,4 @@ message is then used for this.
 
 [coc]: https://github.com/fulls1z3/universal/blob/master/CODE_OF_CONDUCT.md
 [github]: https://github.com/fulls1z3/universal
-[angular-tslint-rules]: https://github.com/fulls1z3/angular-tslint-rules
+[eslint]: https://github.com/eslint/eslint

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2018 Burak Tasci
+Copyright (c) 2021 Burak Tasci
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal