Initializing package with contents terra-framework repo (#1)

* Initializing package with contents terra-framework repo

* Removing npmignore in favor of `files` declaration in package.json. Updating LICENSE/README. Removing unnecessary files.

* PR updates

* Update app.json

Co-Authored-By: Matt Henkes <[email protected]>

* Update docker-compose.yml

Co-Authored-By: Matt Henkes <[email protected]>

* Moving eslint overrides.

* Update package.json

Co-Authored-By: Matt Henkes <[email protected]>

* Update package.json

Co-Authored-By: Matt Henkes <[email protected]>

* Specifying engines

* PR updates

* Update package.json

Co-Authored-By: Matt Henkes <[email protected]>

.dockerignore

@@ -0,0 +1,6 @@
+# add git-ignore syntax here of things you don't want copied into docker image
+
+.git
+*Dockerfile*
+*docker-compose*
+node_modules

.eslintignore

@@ -0,0 +1,5 @@
+node_modules
+coverage
+build
+lib
+**/aggregated-translations/*.*

.gitattributes

@@ -0,0 +1,11 @@
+# This will treat all files as text files and convert to OS's line ending on checkout
+# and back to LF on commit automatically.
+# It also leaves all files detected as binary untouched.
+* text=auto
+
+# These files are text and should be normalized (Convert crlf => lf)
+*.gitattributes text
+.gitignore text
+*.md text
+*.js text eol=lf
+*.jsx text eol=lf

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Set default code owners for all files in repo
+* @mjhenkes @ryanthemanuel @tbiethman @dkasper-was-taken

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,15 @@
+<!--
+  If you're looking to submit a bug report, please fill out this template:
+
+  https://github.com/cerner/terra-application/issues/new?template=BUG_REPORT.md
+
+  If this is a feature request, please fill out this template:
+  
+  https://github.com/cerner/terra-application/issues/new?template=FEATURE_REQUEST.md
+-->
+
+# Issue Description
+<!-- A clear and concise description of what the issue is. -->
+
+## Additional Context / Screenshots
+<!-- Add any other context about the issue here. If applicable, add screenshots to help explain the issue. -->

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,40 @@
+---
+name: 🐛 Bug Report
+about: If something isn't working as expected
+
+---
+
+# Bug Report
+
+## Description
+<!-- A clear and concise description of what the bug is. -->
+<!-- Providing a link to a live example / minimal demo of the problem greatly helps us debug issues. -->
+
+## Steps to Reproduce
+<!-- Please specify the exact steps you took for this bug to occur. -->
+<!-- Provide as much detail as possible so we're able to reproduce these steps. -->
+
+1. 
+2. 
+3. 
+4. 
+
+## Additional Context / Screenshots
+<!-- Add any other context about the problem here. If applicable, add screenshots to help explain. -->
+
+## Expected Behavior
+<!-- A clear and concise description of what you expected to happen. -->
+
+## Possible Solution
+<!--- If you have suggestions to fix the bug, let us know -->
+
+## Environment
+<!-- Include as many relevant details about the environment you experienced the bug in -->
+* Component Name and Version:
+* Browser Name and Version:
+* Node/npm Version: [e.g. Node 8/npm 5]
+* Webpack Version:
+* Operating System and version (desktop or mobile):
+
+## @ Mentions
+<!-- @ Mention anyone on the terra team that you have been working with so far. -->

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,16 @@
+---
+name: 🚀 Feature Request
+about: Submit a proposal for a new feature
+
+---
+
+# Feature Request
+
+## Description
+<!-- A clear and concise description of what the feature is. -->
+
+## Additional Context / Screenshots
+<!-- Add any other context about the feature here. If applicable, add screenshots to help explain. -->
+
+## @ Mentions
+<!-- @ Mention anyone on the terra team that you have been working with so far. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+### Summary
+<!-- Summarize the contents of the code changes. Tag any open issues you believe to be resolved by this pull request. -->
+
+### Additional Details
+<!-- If you have anything else that you think may be relevant to this issue, list it here. Additional information can help us better understand your changes and speed up the review process. -->
+
+@cerner/terra
+<!-- If you haven't done so already, please...
+
+1. Assign yourself to the PR.
+2. Add the appropriate labels
+3. Add your name to the [CONTRIBUTORS.md] file. Adding your name to the [CONTRIBUTORS.md] file signifies agreement to all rights and reservations provided by the [License].
+
+Thanks for contributing to Terra! -->
+
+[CONTRIBUTORS.md]: https://github.com/cerner/terra-application/blob/master/CONTRIBUTORS.md
+[License]: https://github.com/cerner/terra-application/blob/master/License.md

.github/changelog.yml

@@ -0,0 +1,3 @@
+filename: CHANGELOG.md
+include:
+  - /^src\/|^tests\/|^translations\/|^package.json/

.gitignore

@@ -0,0 +1,60 @@
+# From https://github.com/github/gitignore
+#  - Node.gitignore
+#  - Ruby.gitignore
+#  - Sass.gitignore
+
+*.bridgesupport
+*.css.map
+*.gem
+*.log
+*.pid
+*.pid.lock
+*.rbc
+*.seed
+.dat*
+.grunt
+.lock-wscript
+.node_repl_history
+.npm
+.nyc_output
+.repl_history
+.rvmrc
+.DS_Store
+.sass-cache/
+/.bundle/
+/.config
+/.yardoc/
+/_yardoc/
+/coverage/
+/doc/
+/InstalledFiles
+/lib/bundler/man/
+/pkg/
+/rdoc/
+/spec/examples.txt
+/spec/reports/
+/test/tmp/
+/test/version_tmp/
+/tmp/
+/vendor/bundle
+build-iPhoneOS/
+build-iPhoneSimulator/
+build/
+build/Release
+coverage
+jspm_packages
+lib
+lib-cov
+logs
+node_modules
+npm-debug.log*
+pids
+reports`
+target
+**/wdio/__snapshots__/latest
+**/wdio/__snapshots__/diff
+errorScreenshots
+**/aggregated-translations/*.*
+stats.json
+aggregated-themes.js
+package-lock.json

.npmrc

@@ -0,0 +1 @@
+package-lock=false 

.nvmrc

@@ -0,0 +1 @@
+lts/dubnium

.travis.yml

@@ -0,0 +1,65 @@
+language: generic
+sudo: required
+services:
+  - docker
+branches:
+  only:
+    - master
+cache:
+  directories:
+    - $HOME/docker
+env:
+  global:
+    - DOCKER_IMAGE='cerner/terra-application'
+    - TAG="${TRAVIS_PULL_REQUEST_SHA:=latest}"
+before_install:
+  - sudo chown -R travis:travis $HOME/docker
+  # Load cached docker images
+  - if [[ -d $HOME/docker ]]; then ls $HOME/docker/*.tar.gz | xargs -I {file} sh -c "zcat {file} | docker load"; fi
+before_cache:
+  - sudo chown -R travis:travis $HOME/docker
+  - if [ $TRAVIS_TEST_RESULT == 1 ]; then rm -f $HOME/docker/*.tar.gz; fi
+jobs:
+  include:
+    - stage: build
+      before_install: true
+      script:
+        - sudo chown -R travis:travis $HOME/docker
+        - 'rm -f $HOME/docker/*.tar.gz'
+        - travis_wait docker-compose build test-ci
+        - travis_wait docker-compose --verbose pull standalone-chrome
+        - >
+          mkdir -p $HOME/docker && docker images -a --filter='dangling=false' --format '{{.Repository}}:{{.Tag}} {{.ID}}'
+          | xargs -n 2 -t sh -c 'test -e $HOME/docker/$1.tar.gz || docker save $0 | gzip -2 > $HOME/docker/$1.tar.gz'
+    - stage: lint and jest
+      script:
+        - "travis_wait docker-compose run -e HAS_JOSH_K_SEAL_OF_APPROVAL=$HAS_JOSH_K_SEAL_OF_APPROVAL -e TRAVIS_PULL_REQUEST=$TRAVIS_PULL_REQUEST -e TRAVIS_REPO_SLUG=$TRAVIS_REPO_SLUG test-ci bash -c 'npm run lint && npm run jest'"
+    - stage: wdio
+      script:
+        - "travis_wait docker-compose run test-ci npm run wdio"
+    - stage: deploy
+      script: skip
+      before_deploy:
+        - sudo chown -R travis:travis $HOME/docker
+        # Load cached docker images
+        - if [[ -d $HOME/docker ]]; then ls $HOME/docker/*.tar.gz | xargs -I {file} sh -c "zcat {file} | docker load"; fi
+        - "travis_wait docker-compose run --volume=$TRAVIS_BUILD_DIR/build:/opt/terra-application/build -e TERRA_DEV_SITE_NEW_RELIC_LICENSE_KEY='c494ac44c8' -e TERRA_DEV_SITE_NEW_RELIC_APPLICATION_ID='141260567' -e TERRA_DEV_SITE_PUBLIC_PATH='/terra-application/' test-ci npm run compile:prod"
+      deploy:
+        provider: pages
+        skip_cleanup: true
+        github_token: $GITHUB_TOKEN # Set in travis-ci.com dashboard
+        local_dir: build
+        on:
+          branch: master
+    - stage: clean up cache
+      before_install: true
+      script:
+        - sudo chown -R travis:travis $HOME/docker
+        - 'rm -f $HOME/docker/*.tar.gz'
+stages:
+  - build
+  - lint and jest
+  - wdio
+  - name: deploy
+    if: type != pull_request
+  - clean up cache

CHANGELOG.md

@@ -0,0 +1,73 @@
+Changelog
+=========
+
+Unreleased
+----------
+### Added
+* Added ApplicationLoadingOverlay and ApplicationErrorBoundary
+* Integrated ApplicationLoadingOverlay and ApplicationErrorBoundary into ApplicationBase
+* Added NavigationPrompt handling to ApplicationBase
+
+1.11.0 - (October 16, 2019)
+------------------
+### Changed
+* Minor dependency updates
+
+1.10.0 - (October 3, 2019)
+------------------
+### Changed
+* Minor dependency updates
+
+1.9.0 - (September 26, 2019)
+------------------
+### Changed
+* Minor dependency updates
+
+1.8.0 - (September 19, 2019)
+------------------
+### Changed
+* Removed `details` tag from doc-site.
+
+1.7.0 - (September 6, 2019)
+------------------
+### Changed
+* Cleaned up imports in examples and test files
+
+1.6.0 - (August 21, 2019)
+------------------
+### Changed
+* Replaced Object.assign syntax with Object spread syntax
+
+1.5.0 - (August 14, 2019)
+------------------
+### Changed
+* updated package.json test scripts
+
+1.4.0 - (July 30, 2019)
+------------------
+### Removed
+* Removed DEPENDENCIES.md file
+
+1.3.1 - (July 23, 2019)
+------------------
+### Changed
+* Updated DEPENDENCIES.md doc
+
+1.3.0 - (July 23, 2019)
+------------------
+### Changed
+* Normalized terra-doc-template dev dependency version to match other terra-framework packages
+
+1.2.0 - (July 16, 2019)
+------------------
+### Added
+* Added documentation on required peerDependencies
+
+1.1.0 - (July 10, 2019)
+------------------
+### Changed
+* Minor dependency version bump
+
+1.0.0 - (July 2, 2019)
+------------------
+* Initial release

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, 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 or 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. We also have the right to temporarily or permanently ban 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 team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems 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 [http://contributor-covenant.org/version/1/4][version].
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/