Merge pull request #1 from ng-web-apis/initial

chore(all): init

.editorconfig

@@ -0,0 +1,13 @@
+# Editor configuration, see https://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 4
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.md]
+max_line_length = off
+trim_trailing_whitespace = false

.github/CODEOWNERS

@@ -0,0 +1,14 @@
+
+# ==================================================================================
+# ==================================================================================
+#                    @ng-web-apis/resize-observer codeowners
+# ==================================================================================
+# ==================================================================================
+#
+#  Configuration of code ownership and review approvals for the @ng-web-apis/resize-observer repo.
+#
+#  More info: https://help.github.com/articles/about-codeowners/
+#
+
+* @vladimirpotekhin
+# will be requested for review when someone opens a pull request

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,33 @@
+---
+name: 🐞 Bug report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: ''
+assignee: vladimirpotekhin
+---
+
+# 🐞 Bug report
+
+### Description
+
+<!-- A clear and concise description of what the bug is -->
+
+### Reproduction
+
+<!-- Steps to reproduce or, preferably, a demo on StackBlitz or similar service -->
+
+http://www.stackblitz.com/...
+
+### Expected behavior
+
+<!-- A clear and concise description of what you expected to happen -->
+
+### Versions
+
+-   OS: [e.g. iOS]
+-   Browser [e.g. chrome, safari]
+-   Angular [e.g. 8]
+
+### Additional context
+
+<!-- Add any other context about the problem here -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,29 @@
+---
+name: 🚀 Feature request
+about: Suggest an idea for this project
+title: '[FEATURE]'
+labels: ''
+assignee: vladimirpotekhin
+---
+
+# 🚀 Feature request
+
+### Is your feature request related to a problem?
+
+<!-- A clear and concise description of what the problem is. Ex. -->
+<!-- ✍️edit: --> I'm always frustrated when...
+
+### Describe the solution you'd like
+
+<!-- A clear and concise description of what you want to happen -->
+<!-- ✍️edit: -->
+
+### Describe alternatives you've considered
+
+<!-- A clear and concise description of any alternative solutions or features you've considered  -->
+<!-- ✍️edit: -->
+
+### Additional context
+
+<!-- Add any other context or screenshots about the feature request here -->
+<!-- ✍️edit: -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,35 @@
+## PR Checklist
+
+Please check if your PR fulfills the following requirements:
+
+-   [ ] The commit message follows [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0-beta.4/)
+-   [ ] Tests for the changes have been added (for bug fixes / features)
+-   [ ] Docs have been added / updated (for bug fixes / features)
+
+## PR Type
+
+What kind of change does this PR introduce?
+
+<!-- Please check the one that applies to this PR using "x". -->
+
+-   [ ] Bugfix
+-   [ ] Feature
+-   [ ] Refactoring (no functional changes, no api changes)
+-   [ ] Other... Please describe:
+
+## What is the current behavior?
+
+<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
+
+Issue Number: N/A
+
+## What is the new behavior?
+
+## Does this PR introduce a breaking change?
+
+-   [ ] Yes
+-   [ ] No
+
+<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
+
+## Other information

.gitignore

@@ -0,0 +1,49 @@
+# compiled schematics
+schematics/library-starter/*.js
+schematics/library-starter/*.js.map
+schematics/library-starter/*.d.ts
+
+# compiled output
+/dist
+/tmp
+/out-tsc
+# Only exists if Bazel was run
+/bazel-out
+
+# dependencies
+/node_modules
+
+# profiling files
+chrome-profiler-events.json
+speed-measure-plugin.json
+
+# 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
+.history/*
+
+# misc
+/.sass-cache
+/connect.lock
+/coverage
+/libpeerconnection.log
+npm-debug.log
+yarn-error.log
+testem.log
+/typings
+
+# System Files
+.DS_Store
+Thumbs.db

.travis.yml

@@ -0,0 +1,20 @@
+language: node_js
+node_js:
+  - "10"
+cache:
+  directories:
+  - node_modules
+script:
+  - npm run lint
+  - npm run build
+  - npm run build:demo:client
+  - npm run test
+notifications:
+  webhooks: https://coveralls.io/webhook
+deploy:
+  provider: pages
+  skip_cleanup: true
+  github_token: $github_token
+  local_dir: dist/demo/browser
+  on:
+    branch: master

CHANGELOG.md

@@ -0,0 +1 @@
+

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+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
+
+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
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project at ng.web.apis@gmail.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Contributing
+
+> Thank you for considering contributing to our project. Your help if very welcome!
+
+When contributing, it's better to first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change.
+
+All members of our community are expected to follow our [Code of Conduct](CODE_OF_CONDUCT.md).
+Please make sure you are welcoming and friendly in all of our spaces.
+
+## Getting started
+
+In order to make your contribution please make a fork of the repository. After you've pulled
+the code, follow these steps to kick start the development:
+
+1. Run `npm ci` to install dependencies
+2. Run `npm start` to launch demo project where you could test your changes
+3. Use following commands to ensure code quality
+
+```
+npm run lint
+npm run build
+npm run test
+```
+
+## Pull Request Process
+
+1. We follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0-beta.4/)
+   in our commit messages, i.e. `feat(core): improve typing`
+2. Update [README.md](README.md) to reflect changes related to public API and everything relevant
+3. Make sure you cover all code changes with unit tests
+4. When you are ready, create Pull Request of your fork into original repository

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020 Vladimir Potekhin <vladimir.potekh@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.