[koa-shopify-auth] add prefix support post pull [#1413]

.eslintignore

@@ -1,4 +1,7 @@
 node_modules
+coverage
 **/node_modules/*
 **/packages/*.js
 *.d.ts
+**/templates/*
+**/dummy/**

.eslintrc.js

@@ -0,0 +1,57 @@
+module.exports = {
+  extends: [
+    'plugin:@shopify/typescript',
+    'plugin:@shopify/typescript-type-checking',
+    'plugin:@shopify/react',
+    'plugin:@shopify/jest',
+    'plugin:@shopify/prettier',
+  ],
+  parserOptions: {
+    project: [
+      'packages/tsconfig.json',
+      'packages/tsconfig_base.json',
+      'test/tsconfig.eslint.json',
+    ],
+  },
+  rules: {
+    'jest/valid-expect-in-promise': 'off',
+    'import/extensions': 'off',
+    'jsx-a11y/control-has-associated-label': 'off',
+    'node/no-extraneous-require': 'off',
+    'import/no-cycle': 'off',
+    'jest/require-tothrow-message': 'off',
+    'callback-return': 'off',
+    'func-style': 'off',
+    'react/display-name': 'off',
+    '@shopify/restrict-full-import': ['error', 'lodash'],
+    '@shopify/jsx-no-hardcoded-content': 'off',
+    // reports false positives with React's useRef hook
+    'require-atomic-updates': 'off',
+    '@typescript-eslint/no-unnecessary-type-arguments': 'off',
+    '@typescript-eslint/no-unnecessary-condition': 'off',
+    '@typescript-eslint/prefer-readonly': 'off',
+    '@typescript-eslint/ban-types': 'off',
+    '@typescript-eslint/unbound-method': 'off',
+    '@typescript-eslint/no-misused-promises': 'off',
+    '@typescript-eslint/await-thenable': 'off',
+    '@typescript-eslint/no-misused-promises': 'off',
+    'import/no-extraneous-dependencies': 'error',
+  },
+  overrides: [
+    {
+      files: [
+        '**/test/**/*.ts',
+        '**/test/**/*.tsx',
+        '**/tests/**/*.ts',
+        '**/tests/**/*.tsx',
+      ],
+      rules: {
+        // We disable `import/no-extraneous-dependencies` for test files because it
+        // would force releases of `@shopify/react-testing` (and similar devDependencies)
+        // to cause unnecessary package bumps in every package that consumes them.
+        // Test files with extraneous dependencies won't cause runtime errors in production.
+        'import/no-extraneous-dependencies': 'off',
+      },
+    },
+  ],
+};

.github/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 making 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/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 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/

.github/CONTRIBUTING.md

@@ -0,0 +1,109 @@
+# Quilt: a contributor's guide
+
+This guide is tailored to Shopifolk, although we welcome contributions from [the broader development community](#external-contributors) as well.
+
+## [Code of conduct](./CODE_OF_CONDUCT.md).
+
+Shopify has adopted a Code of Conduct that we expect Quilt contributors to adhere to. Please read the [full text](./CODE_OF_CONDUCT.md) so that you can understand what actions will and will not be tolerated.
+
+## Ways to contribute
+
+There are many ways to contribute to Quilt, some of which are:
+
+- Filing [bug reports](https://github.com/Shopify/quilt/issues/new?template=BUG_REPORT.md)
+- Requesting new features or packages via [an issue](https://github.com/Shopify/quilt/issues/new/choose)
+  - Bringing up areas for enhancement
+- Hacking away on an issue from our [backlog](https://github.com/Shopify/quilt/issues)
+- Improving tests or documentation
+
+Want to contribute, but not sure how? Find us on Slack in `#web-foundation-tech`.
+
+## Development
+
+### Getting Started
+
+```bash
+dev clone quilt
+dev up
+```
+
+[what is dev?](#what-is-dev)
+
+### Getting productive
+
+We are adding documentation as we go in the [Web Foundation repo](https://github.com/Shopify/web-foundation). There you will find our [decision records](https://github.com/Shopify/web-foundation/tree/master/Decision%20records), [principles](https://github.com/Shopify/web-foundation/tree/master/Principles), [best practices](https://github.com/Shopify/web-foundation/tree/master/Best%20practices) and [styleguides](https://github.com/Shopify/web-foundation/tree/master/Styleguides) for writing and [testing](https://github.com/Shopify/web-foundation/blob/master/Best%20practices/Testing.md) different kinds of components.
+
+The [documentation](../documentation) directory in this repo covers the more granular technical aspects of this project. Of particular note for new folks are the following:
+
+- [Guides](../documentation/guides): a set of guides to help you get started developing with `quilt`. Of particular note for developers just starting on the project is our guide to [creating a new package](../documentation/guides/creating-a-new-package.md).
+- [FAQ](../documentation/FAQ.md): common questions about the project in general, as well as some of the technical pieces within.
+- [Resources](../documentation/resources.md): good resources for understanding this project’s tech stack.
+- [Getting started](../documentation/getting-started.md): some tools we recommend for getting the most out of this project.
+
+## Testing your changes in a local project
+
+To try out your changes in another locally cloned project, you can use `yarn tophat <package-name-without-@shopify-prefix> <relative-path-to-project>`. Using this command rather than `yarn link` will set up a watcher let you make changes without needing to rerun any commands.
+
+Example: To test my changes to `@shopify/react-form-state` in my local project named `cool-proj`, I would run `yarn tophat react-form-state ../path/to/cool-proj`.
+
+Notes: If the package you are testing has dependencies inside Quilt itself, you will need to run `dev build` first. If you are using a build system in the consumer of the package, you may need to clear your build folder.
+
+More usage instructions on the `tophat` command can be [found here](https://github.com/Shopify/webgen/blob/master/docs/TOPHAT.md).
+
+### Emoji commits
+
+We have found that prefacing a commit message or PR title with an emoji can be a great way to improve the developer experience when browsing the repo code. Additionally, it is a terse way to convey information. Many of our contributors have found the guide at https://gitmoji.carloscuesta.me/ to be helpful in preserving this dynamic.
+
+### Documentation
+
+If your change affects the public API of any packages within Quilt (i.e. adding or
+changing arguments to a function, adding a new function, changing the
+return value, etc), please ensure the documentation is also updated to
+reflect this. Documentation is in the `README.md` files of each package. If further documentation is needed please communicate via Github Issues.
+
+### Testing
+
+The packages in Quilt are used in mission-critical production scenarios. As such, we try not to merge any untested code. The coverage doesn't strictly need to be 100% across the board, but testing should remain a primary concern.
+
+To run the full test suite, simply run `dev test`. In order for tests to run properly, you may need to first run `dev build`
+
+### TODO Comments
+
+TODO comments may seem like a great placeholder for work in progress. We prefer to handle this in a different way, using a combination of feature branches and github issues.
+
+#### Follow-up Github issues
+
+If your changes are complete in functionality, but you're not quite happy with auxillary things like documentation or testing, then feel free to make a github issue to track the work that needs to be done. These issues should be linked in the PRs that need a bit more work. This will allow context to be drawn from the code in a more trackable way than a TODO comment. Also, it allows the PR reviewers to see that the documentation or testing is purposefully incomplete and that an appropriate issue exists to track the follow-up work.
+
+#### Feature branches
+
+Another option, if you'd like to break work down into reviewable chunks, is to use a feature branch. This would be an initially empty branch that contains the entirety of your feature. Additional units of work can be distributed across several PRs into the feature branch, merged independently, and then the feature branch can be merged as a complete unit into the master branch, when it's ready.
+
+## Releasing
+
+The release process currently involves some manual steps to complete. Please ping Web Foundations ATC in the `#web-foundation-tech` Slack channel when you're ready to merge a new PR into `master`, and we will orchestrate a new release. The repo owner can follow [this guide](../documentation/guides/release-and-deploy.md) to create a release.
+
+**Note** Version numbers in `package.json` files should never be altered manually. This will be done via scripts as part of the release process.
+
+## External Contributors
+
+### Getting started
+
+To start working on the codebase, first fork the repo, then clone it:
+
+```
+git clone [email protected]:your-username/quilt.git
+```
+
+_Note: replace "your-username" with your Github handle_
+
+Install the project's dependencies (make sure you first have [yarn](https://yarnpkg.com/) installed):
+
+```
+yarn
+yarn lerna bootstrap
+```
+
+### What is dev?
+
+`dev` is a tool to standardize a small set of common tasks across all projects at Shopify. If you're wondering how to execute the `dev <cmd>` commands as an external contributor, you can see where they are defined in this project's [`dev.yml`](../dev.yml) file, which is pretty self-explanatory.

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,35 @@
+---
+name: '🐛 Bug Report'
+about: Something isn't working
+---
+
+## Overview
+
+...
+
+## Consuming repo
+
+> What repo were you working in when this issue occurred?
+
+...
+
+## Labels
+
+- [ ] Add the `Type: Bug` label to this issue.
+
+### Area
+
+- [ ] Add any relevant `Area: <area>` labels to this issue
+
+### Scope
+
+- Is this issue related to a specific package?
+
+  - [ ] Tag it with the `Package: <package_name>` label.
+
+---
+
+## Checklist
+
+- [ ] Please delete the labels section before submitting your issue
+- [ ] I have described this issue in a way that is actionable (if possible)

.github/ISSUE_TEMPLATE/ENHANCEMENT.md

@@ -0,0 +1,35 @@
+---
+name: '📈 Enhancement'
+about: Enhancement to our codebase that isn't a adding or changing a feature
+---
+
+## Overview
+
+...
+
+## Motivation
+
+> What inspired this enhancement? What makes you think this should be in `quilt`?
+
+...
+
+## Labels
+
+- [ ] Add the `Type: Enhancement` label to this issue.
+
+### Area
+
+- [ ] Add any relevant `Area: <area>` labels to this issue
+
+### Scope
+
+- Is this issue related to a specific package?
+
+  - [ ] Tag it with the `Package: <package_name>` label.
+
+---
+
+## Checklist
+
+- [ ] Please delete the labels section before submitting your issue
+- [ ] I have described this issue in a way that is actionable (if possible)

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,44 @@
+---
+name: '🙌 Feature Request'
+about: Suggest a new feature, or changes to an existing one
+---
+
+## Overview
+
+...
+
+## Type
+
+- [ ] New feature
+- [ ] Changes to existing features
+
+## Motivation
+
+> What inspired this feature request? What problems were you facing,
+> or what else makes you think this should be in `quilt`?
+
+...
+
+## Labels
+
+- [ ] Add the `Type: Feature Request` label to this issue.
+
+### Area
+
+- [ ] Add any relevant `Area: <area>` labels to this issue
+
+### Scope
+
+- Is this issue related to a specific package?
+
+  - [ ] Tag it with the `Package: <package_name>` label.
+
+- Is it related to a new package?
+  - [ ] Tag it with the `New package` Label
+
+---
+
+## Checklist
+
+- [ ] Please delete the labels section before submitting your issue
+- [ ] I have described this issue in a way that is actionable (if possible)

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,25 @@
+## Description
+
+Fixes (issue #)
+
+<!--
+Please include a summary of what you want to achieve in this pull request. Remember to indicate the affected package(s).
+-->
+
+## Type of change
+
+<!--
+If this pull request changes multiple packages, please indicate the type of change for each package.
+
+If this is a new package, you may disregard this section.
+
+Please delete options that are not relevant.
+-->
+
+- [ ] <!--Package Name--> Patch: Bug/ Documentation fix (non-breaking change which fixes an issue or adds documentation)
+- [ ] <!--Package Name--> Minor: New feature (non-breaking change which adds functionality)
+- [ ] <!--Package Name--> Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)
+
+## Checklist
+
+- [ ] I have added a changelog entry, prefixed by the type of change noted above

.github/probots.yml

@@ -0,0 +1,2 @@
+enabled:
+  - cla