Merge next

.gitattributes

@@ -1,2 +1 @@
-* text=auto
-*.js text eol=lf
+* text=auto eol=lf

.prettierrc.js

@@ -0,0 +1,18 @@
+module.exports = {
+  arrowParens: 'avoid',
+  bracketSpacing: false,
+  endOfLine: 'lf',
+  htmlWhitespaceSensitivity: 'css',
+  insertPragma: false,
+  jsxBracketSameLine: false,
+  jsxSingleQuote: false,
+  printWidth: 80,
+  proseWrap: 'always',
+  quoteProps: 'as-needed',
+  requirePragma: false,
+  semi: false,
+  singleQuote: true,
+  tabWidth: 2,
+  trailingComma: 'all',
+  useTabs: false,
+}

.travis.yml

@@ -1,25 +1,23 @@
 language: node_js
 
-node_js:
-  - '8'
-  - '10'
-  - '12'
-
-sudo: false
+cache: npm
 notifications:
   email: false
-cache:
-  directories:
-    - node_modules
-
-script: yarn validate
+node_js:
+  - 10.18
+  - 12
+  - node
+install: npm install
+script:
+  - npm run validate
+  - npx codecov@3
+branches:
+  only:
+    - master
+    - next
 
 jobs:
   include:
     - stage: release
-      node_js: lts/*
-      script: yarn build
-      deploy:
-        provider: script
-        skip_cleanup: true
-        script: 'node src travis-after-success'
+      node_js: 12
+      script: node src travis-release

CHANGELOG.md

@@ -1,4 +1,5 @@
 # CHANGELOG
 
-The changelog is automatically updated using [semantic-release](https://github.com/semantic-release/semantic-release).
-You can see it on the [releases page](../../releases).
+The changelog is automatically updated using
+[semantic-release](https://github.com/semantic-release/semantic-release). You
+can see it on the [releases page](../../releases).

CONTRIBUTING.md

@@ -2,8 +2,8 @@
 
 Thanks for being willing to contribute!
 
-**Working on your first Pull Request?** You can learn how from this _free_ series
-[How to Contribute to an Open Source Project on GitHub][egghead]
+**Working on your first Pull Request?** You can learn how from this _free_
+series [How to Contribute to an Open Source Project on GitHub][egghead]
 
 ## Project setup
 
@@ -21,24 +21,23 @@ Thanks for being willing to contribute!
 > git branch --set-upstream-to=upstream/master master
 > ```
 >
-> This will add the original repository as a "remote" called "upstream,"
-> Then fetch the git information from that remote, then set your local `master`
-> branch to use the upstream master branch whenever you run `git pull`.
-> Then you can make all of your pull request branches based on this `master`
-> branch. Whenever you want to update your version of `master`, do a regular
-> `git pull`.
+> This will add the original repository as a "remote" called "upstream," Then
+> fetch the git information from that remote, then set your local `master`
+> branch to use the upstream master branch whenever you run `git pull`. Then you
+> can make all of your pull request branches based on this `master` branch.
+> Whenever you want to update your version of `master`, do a regular `git pull`.
 
 ## Committing and Pushing changes
 
 This project uses [`semantic-release`][semantic-release] to do automatic
-releases and generate a changelog based on the commit history. So we follow
-[a convention][convention] for commit messages. You don't have to follow this
+releases and generate a changelog based on the commit history. So we follow [a
+convention][convention] for commit messages. You don't have to follow this
 convention if you don't want to. Just know that when we merge your commit, we'll
 probably use "Squash and Merge" so we can change the commit message :)
 
 Please make sure to run the tests before you commit your changes. You can run
-`npm run test:update` which will update any snapshots that need updating.
-Make sure to include those changes (if they exist) in your commit.
+`npm run test:update` which will update any snapshots that need updating. Make
+sure to include those changes (if they exist) in your commit.
 
 ### opt in/out of git hooks
 
@@ -53,10 +52,10 @@ pre-commit
 ```
 
 One of the things that the git hooks does is automatically format the files you
-change. It does this by reformating the entire file and running `git add` on
-the file after. This breaks workflows where you're trying to commit portions of
-the file only. You can always run your commit with `--no-verify`, but if this
-is a bummer to your workflow, you can add an `.opt-out` file with the contents:
+change. It does this by reformating the entire file and running `git add` on the
+file after. This breaks workflows where you're trying to commit portions of the
+file only. You can always run your commit with `--no-verify`, but if this is a
+bummer to your workflow, you can add an `.opt-out` file with the contents:
 
 ```
 autoformat
@@ -69,7 +68,9 @@ Please checkout the [the open issues][issues]
 Also, please watch the repo and respond to questions/bug reports/feature
 requests! Thanks!
 
-[egghead]: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github
+[egghead]:
+  https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github
 [semantic-release]: https://npmjs.com/package/semantic-release
-[convention]: https://github.com/conventional-changelog/conventional-changelog-angular/blob/ed32559941719a130bb0327f886d6a32a8cbc2ba/convention.md
+[convention]:
+  https://github.com/conventional-changelog/conventional-changelog-angular/blob/ed32559941719a130bb0327f886d6a32a8cbc2ba/convention.md
 [issues]: https://github.com/hoverinc/hover-javascript/issues

Dockerfile

@@ -1,3 +1,3 @@
-FROM node:10.16.3-alpine
+FROM node:10.19.0-alpine
 RUN apk update && apk upgrade && apk add --no-cache git openssh
 RUN npm config set unsafe-perm true

README.md

@@ -1,3 +1,9 @@
+<p align="center">
+  <a href="https://codefund.io/properties/447/visit-sponsor">
+    <img src="https://codefund.io/properties/447/sponsor" />
+  </a>
+</p>
+
 <div align="center">
 <h1>@hover/javascript 🛠📦</h1>
 
@@ -8,18 +14,17 @@
 
 [![Build Status][build-badge]][build]
 [![Code Coverage][coverage-badge]][coverage]
-[![version][version-badge]][package]
-[![MIT License][license-badge]][license]
+[![version][version-badge]][package] [![MIT License][license-badge]][license]
 
 ## The problem
 
-~~I~~ **We** do a bunch of open source and want to make it easier to maintain so many
-projects.
+~~I~~ **We** do a bunch of open source and want to make it easier to maintain so
+many projects.
 
 ## This solution
 
-This is a CLI that abstracts away all configuration for ~~my~~ **our** open source projects
-for linting, testing, building, and more.
+This is a CLI that abstracts away all configuration for ~~my~~ **our** open
+source projects for linting, testing, building, and more.
 
 ## Table of Contents
 
@@ -44,11 +49,12 @@ yarn add -D @hover/javascript
 
 ## Usage
 
-This is a CLI and exposes a bin called `hover-scripts`. You'll find all available scripts in `src/scripts`.
+This is a CLI and exposes a bin called `hover-scripts`. You'll find all
+available scripts in `src/scripts`.
 
 This project actually dogfoods itself. If you look in the `package.json`, you'll
-find scripts with `node src {scriptName}`. This serves as an example of some
-of the things you can do with `hover-scripts`.
+find scripts with `node src {scriptName}`. This serves as an example of some of
+the things you can do with `hover-scripts`.
 
 ### Overriding Config
 
@@ -92,8 +98,8 @@ module.exports = Object.assign(jestConfig, {
 
 > Note: `hover-scripts` intentionally does not merge things for you when you
 > start configuring things to make it less magical and more straightforward.
-> Extending can take place on your terms. ~~I~~ _Kent_ think[s] this is
-> actually a great way to do this.
+> Extending can take place on your terms. ~~I~~ _Kent_ think[s] this is actually
+> a great way to do this.
 >
 > For the record, so do I (Jamie)
 
@@ -103,9 +109,12 @@ MIT
 
 [npm]: https://www.npmjs.com/
 [node]: https://nodejs.org
-[build-badge]: https://g.codefresh.io/api/badges/pipeline/hoverinc/npm%2Fjavascript?type=cf-1
-[build]: https://g.codefresh.io/public/accounts/hoverinc/pipelines/5d4cb5d4e41f3722d4dfdb94
-[coverage-badge]: https://img.shields.io/codecov/c/github/hoverinc/hover-javascript.svg
+[build-badge]:
+  https://g.codefresh.io/api/badges/pipeline/hoverinc/npm%2Fjavascript?type=cf-1
+[build]:
+  https://g.codefresh.io/public/accounts/hoverinc/pipelines/5d4cb5d4e41f3722d4dfdb94
+[coverage-badge]:
+  https://img.shields.io/codecov/c/github/hoverinc/hover-javascript.svg
 [coverage]: https://codecov.io/github/hoverinc/hover-javascript
 [version-badge]: https://img.shields.io/npm/v/@hover/javascript.svg
 [package]: https://www.npmjs.com/package/@hover/javascript

codefresh.yml

@@ -6,6 +6,7 @@ indicators:
         branch:
           only:
             - master
+            - next
 
 stages:
   - prepare
@@ -20,12 +21,12 @@ steps:
     revision: '${{CF_BRANCH}}'
   build:
     stage: build
-    image: node:10.16.3-alpine
+    image: node:10.19.0-alpine
     commands:
       - yarn install
   test:
     stage: build
-    image: node:10.16.3-alpine
+    image: node:10.19.0-alpine
     commands:
       - yarn validate
   releaser:

other/CODE_OF_CONDUCT.md

@@ -20,9 +20,9 @@
 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.
+size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual identity
+and orientation.
 
 ## Our Standards
 
@@ -52,11 +52,11 @@ 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.
+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
 
@@ -73,17 +73,18 @@ Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported by contacting the project team at kent+coc@doddsfamily.us. 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.
+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]
+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/