Merge branch 'master' into next-8-dev

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -9,26 +9,26 @@ assignees: ''
 
 ## Bug Report
 
-<!-- Check this if you would like to implement a PR, we are more than happy to help you go through the process !-->
+<!-- If you would like to implement a PR, we are more than happy to help you go through the process!-->
 - [ ] I would like to work on a fix!
 
 <!--
 @babel/eslint-parser:
   If you are having issues with JSX you might want to check out eslint-plugin-react. If there's an issue with new experimental syntax you might need check if it's supported by @babel/eslint-plugin.
 -->
 
-**Current Behavior**
+**Current behavior**
 A clear and concise description of the behavior.
 
-- [REPL](babeljs.io/repl), [Codesandbox](https://codesandbox.io/s/babel-repl-custom-plugin-7s08o?file=/src/index.js), or GitHub Repo link if applicable:
+- [REPL](babeljs.io/repl), [Codesandbox](https://codesandbox.io/s/babel-repl-custom-plugin-7s08o?file=/src/index.js), or GitHub Repo helps!
 
 **Input Code**
 
 ```js
 var your => (code) => here;
 ```
 
-**Expected behavior/code**
+**Expected behavior**
 A clear and concise description of what you expected to happen (or code).
 
 **Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)**
@@ -54,5 +54,5 @@ A clear and concise description of what you expected to happen (or code).
 **Possible Solution**
 <!--- If you have suggestions on a fix for the bug -->
 
-**Additional context/Screenshots**
-Add any other context about the problem here. If applicable, add screenshots to help explain.
+**Additional context**
+Add any other context about the problem here. Or a screenshot if applicable

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -1,6 +1,6 @@
 ---
 name: "\U0001F680 Feature Request"
-about: "I have a suggestion (and may want to implement it \U0001F642)!"
+about: "I have a specific suggestion for Babel!"
 title: ''
 labels: 'i: enhancement, i: needs triage'
 assignees: ''
@@ -12,15 +12,12 @@ assignees: ''
 <!-- Check this if you would like to implement a PR, we are more than happy to help you go through the process !-->
 - [ ] I would like to work on this feature!
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I have an issue when [...]
+**Is your feature request related to a problem?**
+A concise description of what the problem is. Ex. I have an issue when [...]
 
 **Describe the solution you'd like**
-A clear and concise description of what you want to happen. Add any considered drawbacks.
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+**Describe alternatives 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 the docs.
-Maybe a screenshot or design?
+**Documentation, Adoption, Migration Strategy**
+If you can, explain how users will be able to use this and how it might be documented. Maybe a mock-up?

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 📦 "No matching version found"
+    url: https://gist.github.com/hzoo/df94af2d2ec48696e683b772c775aa67
+    about: You may have an npm error related to proxies/caching.
+  - name: 🗣 Ask a Question, Discuss
+    url: https://github.com/babel/babel/discussions
+    about: How does X work 🤔? I made this! I have an idea..
+  - name: 💡 Propose an RFC
+    url: https://github.com/babel/rfcs
+    about: To suggest a new option or substantial change.
+  - name: 🤗 Support the Project
+    url: https://github.com/sponsors/babel
+    about: Support the Babel team financially.

.github/workflows/coverage.yml

@@ -5,23 +5,15 @@ on: [push, pull_request]
 jobs:
   build:
     runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        node-version: [13.x]
     steps:
       - name: Checkout code
-        uses: actions/checkout@v1
-      - name: Use Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@v1
+        uses: actions/checkout@v2
+      - name: Use Node.js latest
+        uses: actions/setup-node@v2-beta
         with:
-          node-version: ${{ matrix.node-version }}
-      - name: Environment log
-        id: env
-        run: |
-          yarn --version
+          node-version: "*"
       - name: Generate coverage report
         run: |
-          yarn --version
           make -j test-ci-coverage
       - name: Upload coverage report
         uses: codecov/codecov-action@v1

.gitpod.yml

@@ -0,0 +1,40 @@
+# List the start up tasks. You can start them in parallel in multiple terminals. See https://www.gitpod.io/docs/config-start-tasks/
+tasks:
+  - init: make bootstrap
+    command: make watch
+  - openMode: split-right
+    command: |-
+      clear && echo '
+      Welcome to Gitpod!
+
+      If you haven'\''t forked Babel yet and you want to prepare a PR, you can use
+      the Ctrl+P (or ⌘P) shortcut, type `>Fork` and press ENTER: Gitpod\ will
+      create the fork for you.
+
+      <-- The other terminal is building Babel. It should automatically rebuild
+          when you change a file, so you don'\''t need to worry about it.
+          If it'\''s still building, please wait until it'\''s finished!
+
+      If you want to run the tests, you can run `yarn jest` in this terminal,
+      or filter by package name (for example, `yarn jest babel-parser`).
+      '
+
+#' # <-- This is just because the gitpod theme has broken syntax highlighting
+
+github:
+  # https://www.gitpod.io/docs/prebuilds/#configure-prebuilds
+  prebuilds:
+    master: true
+    branches: true
+    pullRequests: true
+    pullRequestsFromForks: true
+    addCheck: true
+    addComment: false
+    addBadge: true
+    addLabel: false
+
+vscode:
+  extensions:
+    - dbaeumer.vscode-eslint@2.1.5:9Wg0Glx/TwD8ElFBg+FKcQ==
+    - esbenp.prettier-vscode@5.0.0:qca7d0cHbKkrkb5rvNlpcg==
+    - flowtype.flow-for-vscode@1.5.0:AwOT6wgHTF43loZQCAUMLA==