Adopt config from other Testing Library repos (fix #13)

.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,40 @@
+<!--
+Thanks for your interest in the project. I appreciate bugs filed and PRs submitted!
+Please make sure that you are familiar with and follow the Code of Conduct for
+this project.
+
+Please fill out this template with all the relevant information so we can
+understand what's going on and fix the issue.
+
+I'll probably ask you to submit the fix (after giving some direction). If you've
+never done that before, that's great! Check this free short video tutorial to
+learn how: https://kcd.im/pull-request
+
+
+If this is an issue with the documentation, please file an issue in the docs repo:
+https://github.com/testing-library/testing-library-docs
+
+-->
+
+- Testing Library Recorder Extension version:
+- Testing Library versions:
+- Testing Framework and version:
+  <!-- are you using jest, mocha, puppeteer, ava? And what version? -->
+- DOM Environment:
+  <!-- If you're using jsdom (the default with jest), what version? Otherwise, what browser and version are you running tests in? -->
+
+Relevant code or config
+
+```js
+
+```
+
+What you did:
+
+What happened:
+
+<!-- Please provide the full error message/screenshots/anything -->
+
+Problem description:
+
+Suggested solution:

.github/ISSUE_TEMPLATE/Bug_Report.md

@@ -0,0 +1,65 @@
+---
+name: 🐛 Bug Report
+about: Bugs, missing documentation, or unexpected behavior 🤔.
+---
+
+<!--
+
+* Please fill out this template with all the relevant information so we can
+  understand what's going on and fix the issue. We appreciate bugs filed and PRs
+  submitted!
+
+* Please make sure that you are familiar with and follow the Code of Conduct for
+  this project.
+
+We'll probably ask you to submit the fix (after giving some direction). If
+you've never done that before, that's great! Check this free short video
+tutorial to learn how: https://kcd.im/pull-request
+
+If this is an issue with the documentation, please file an issue in the docs repo:
+https://github.com/testing-library/testing-library-docs
+-->
+
+- Testing Library Recorder Extension version:
+- Testing Library versions:
+- Testing Framework and version:
+  <!-- are you using jest, mocha, puppeteer, ava? And what version? -->
+- DOM Environment:
+  <!-- If you're using jsdom (the default with jest), what version? Otherwise, what browser and version are you running tests in? -->
+
+### Relevant code or config:
+
+```js
+var your => (code) => here;
+```
+
+### What you did:
+
+<!-- What you were doing -->
+
+### What happened:
+
+<!-- Please provide the full error message/screenshots/anything -->
+
+### Reproduction:
+
+<!--
+If possible, please create a repository that reproduces the issue with the
+minimal amount of code possible.
+
+Repository template: https://github.com/testing-library/dom-testing-library-template
+
+Or if you can, try to reproduce the issue in a Codesandbox. You can fork the one
+here: https://codesandbox.io/s/5z6x4r7n0p
+-->
+
+### Problem description:
+
+<!-- Please describe why the current behavior is a problem -->
+
+### Suggested solution:
+
+<!--
+It's ok if you don't have a suggested solution, but it really helps if you could
+do a little digging to come up with some suggestion of how to improve things.
+-->

.github/ISSUE_TEMPLATE/Feature_Request.md

@@ -0,0 +1,50 @@
+---
+name: 💡 Feature Request
+about: I have a suggestion (and might want to implement myself 🙂)!
+---
+
+<!--
+
+Vote on feature requests by adding a 👍. This helps maintainers prioritize what
+to work on.
+
+* Please fill out this template with all the relevant information so we can
+  understand what's going on and fix the issue. We appreciate bugs filed and PRs
+  submitted!
+
+* Please make sure that you are familiar with and follow the Code of Conduct for
+  this project.
+
+It'd be great if after the discussion you're the one who submits the PR that
+implements this feature. If you've never done that before, that's great! Check
+this free short video tutorial to learn how: https://kcd.im/pull-request
+
+
+If this is an issue with the documentation, please file an issue in the docs repo:
+https://github.com/testing-library/testing-library-docs
+-->
+
+### Describe the feature you'd like:
+
+<!--
+A clear and concise description of what you want to happen. Add any considered
+drawbacks.
+-->
+
+### Suggested implementation:
+
+<!-- Helpful but optional 😀 -->
+
+### Describe alternatives you've considered:
+
+<!--
+A clear and concise description of any alternative solutions or features you've
+considered.
+-->
+
+### Teachability, Documentation, Adoption, Migration Strategy:
+
+<!--
+If you can, explain how users will be able to use this and possibly write out a
+version of the docs.
+-->

.github/ISSUE_TEMPLATE/Question.md

@@ -0,0 +1,19 @@
+---
+name: ❓ Support Question
+about: 🛑 If you have a question 💬, please check out our support channels!
+---
+
+------------ 👆 Click "Preview"!
+
+Issues on GitHub are intended to be related to problems with the library itself
+and feature requests so we recommend not using this medium to ask them here 😁.
+
+---
+
+## ❓ Support Forums
+
+- Discord https://discord.gg/testing-library
+- Stack Overflow
+  https://stackoverflow.com/questions/tagged/react-testing-library
+
+**ISSUES WHICH ARE QUESTIONS WILL BE CLOSED**

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,43 @@
+<!--
+Thanks for your interest in the project. Bugs filed and PRs submitted are appreciated!
+
+Please make sure that you are familiar with and follow the Code of Conduct for
+this project.
+
+Also, please make sure you're familiar with and follow the instructions in the
+contributing guidelines (found in the CONTRIBUTING.md file).
+
+If you're new to contributing to open source projects, you might find this free
+video course helpful: https://kcd.im/pull-request
+
+Please fill out the information below to expedite the review and (hopefully)
+merge of your pull request!
+-->
+
+<!-- What changes are being made? (What feature/bug is being fixed here?) -->
+
+**What**:
+
+<!-- Why are these changes necessary? -->
+
+**Why**:
+
+<!-- How were these changes implemented? -->
+
+**How**:
+
+<!-- Have you done all of these things?  -->
+
+**Checklist**:
+
+<!-- add "N/A" to the end of each line that's irrelevant to your changes -->
+
+<!-- to check an item, place an "x" in the box like so: "- [x] Documentation" -->
+
+- [ ] Documentation added to the README.md file or
+      [docs site](https://github.com/testing-library/testing-library-docs)
+- [ ] Tests
+- [ ] Ready to be merged
+      <!-- In your opinion, is this ready to be merged as soon as it's reviewed? -->
+
+<!-- feel free to add additional comments -->

.github/workflows/validate.yml

@@ -0,0 +1,45 @@
+name: validate
+on:
+  push:
+    branches:
+      # Match SemVer major release branches
+      # e.g. "12.x" or "8.x"
+      - '[0-9]+.x'
+      - 'main'
+      - 'next'
+      - 'next-major'
+      - 'beta'
+      - 'alpha'
+      - '!all-contributors/**'
+  pull_request: {}
+jobs:
+  main:
+    # ignore all-contributors PRs
+    if: ${{ !contains(github.head_ref, 'all-contributors') }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: 🛑 Cancel Previous Runs
+        uses: styfle/[email protected]
+
+      - name: ⬇️ Checkout repo
+        uses: actions/checkout@v3
+        with:
+          # required by codecov/codecov-action
+          fetch-depth: 0
+
+      - name: ⎔ Setup node
+        uses: actions/setup-node@v3
+
+      - name: 📥 Download deps
+        uses: bahmutov/npm-install@v1
+
+      - name: Verify format (`npm run format` committed?)
+        run: npm run format -- --check --no-write
+
+      - name: ▶️ Run validate script
+        run: npm run validate
+
+      - name: ⬆️ Upload coverage report
+        uses: codecov/codecov-action@v1
+        with:
+          fail_ci_if_error: true

.gitignore

@@ -1,104 +1,3 @@
-# Logs
-logs
-*.log
-npm-debug.log*
-yarn-debug.log*
-yarn-error.log*
-lerna-debug.log*
-
-# Diagnostic reports (https://nodejs.org/api/report.html)
-report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
-
-# Runtime data
-pids
-*.pid
-*.seed
-*.pid.lock
-
-# Directory for instrumented libs generated by jscoverage/JSCover
-lib-cov
-
-# Coverage directory used by tools like istanbul
+node_modules
 coverage
-*.lcov
-
-# nyc test coverage
-.nyc_output
-
-# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
-.grunt
-
-# Bower dependency directory (https://bower.io/)
-bower_components
-
-# node-waf configuration
-.lock-wscript
-
-# Compiled binary addons (https://nodejs.org/api/addons.html)
-build/Release
-
-# Dependency directories
-node_modules/
-jspm_packages/
-
-# TypeScript v1 declaration files
-typings/
-
-# TypeScript cache
-*.tsbuildinfo
-
-# Optional npm cache directory
-.npm
-
-# Optional eslint cache
-.eslintcache
-
-# Microbundle cache
-.rpt2_cache/
-.rts2_cache_cjs/
-.rts2_cache_es/
-.rts2_cache_umd/
-
-# Optional REPL history
-.node_repl_history
-
-# Output of 'npm pack'
-*.tgz
-
-# Yarn Integrity file
-.yarn-integrity
-
-# dotenv environment variables file
-.env
-.env.test
-
-# parcel-bundler cache (https://parceljs.org/)
-.cache
-
-# Next.js build output
-.next
-
-# Nuxt.js build / generate output
-.nuxt
 dist
-
-# Gatsby files
-.cache/
-# Comment in the public line in if your project uses Gatsby and *not* Next.js
-# https://nextjs.org/blog/next-9-1#public-directory-support
-# public
-
-# vuepress build output
-.vuepress/dist
-
-# Serverless directories
-.serverless/
-
-# FuseBox cache
-.fusebox/
-
-# DynamoDB Local files
-.dynamodb/
-
-# TernJS port file
-.tern-port

.huskyrc.js

@@ -0,0 +1 @@
+module.exports = require('kcd-scripts/husky')