update eslint. lint.

Author: jonschlinkert

.github/contributing.md

@@ -0,0 +1,58 @@
+# Contributing to fill-range
+
+First and foremost, thank you! We appreciate that you want to contribute to fill-range, your time is valuable, and your contributions mean a lot to us.
+
+**What does "contributing" mean?**
+
+Creating an issue is the simplest form of contributing to a project. But there are many ways to contribute, including the following:
+
+- Updating or correcting documentation
+- Feature requests
+- Bug reports
+
+If you'd like to learn more about contributing in general, the [Guide to Idiomatic Contributing](https://github.com/jonschlinkert/idiomatic-contributing) has a lot of useful information.
+
+**Showing support for fill-range**
+
+Please keep in mind that open source software is built by people like you, who spend their free time creating things the rest the community can use.
+
+Don't have time to contribute? No worries, here are some other ways to show your support for fill-range:
+
+- star the [project](https://github.com/jonschlinkert/fill-range)
+- tweet your support for fill-range
+
+## Issues
+
+### Before creating an issue
+
+Please try to determine if the issue is caused by an underlying library, and if so, create the issue there. Sometimes this is difficult to know. We only ask that you attempt to give a reasonable attempt to find out. Oftentimes the readme will have advice about where to go to create issues.
+
+Try to follow these guidelines
+
+- **Investigate the issue**:
+- **Check the readme** - oftentimes you will find notes about creating issues, and where to go depending on the type of issue.
+- Create the issue in the appropriate repository.
+
+### Creating an issue
+
+Please be as descriptive as possible when creating an issue. Give us the information we need to successfully answer your question or address your issue by answering the following in your issue:
+
+- **version**: please note the version of fill-range are you using
+- **extensions, plugins, helpers, etc** (if applicable): please list any extensions you're using
+- **error messages**: please paste any error messages into the issue, or a [gist](https://gist.github.com/)
+
+## Above and beyond
+
+Here are some tips for creating idiomatic issues. Taking just a little bit extra time will make your issue easier to read, easier to resolve, more likely to be found by others who have the same or similar issue in the future.
+
+- read the [Guide to Idiomatic Contributing](https://github.com/jonschlinkert/idiomatic-contributing)
+- take some time to learn basic markdown. This [markdown cheatsheet](https://gist.github.com/jonschlinkert/5854601) is super helpful, as is the GitHub guide to [basic markdown](https://help.github.com/articles/markdown-basics/).
+- Learn about [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). And if you want to really go above and beyond, read [mastering markdown](https://guides.github.com/features/mastering-markdown/).
+- use backticks to wrap code. This ensures that code will retain its format, making it much more readable to others
+- use syntax highlighting by adding the correct language name after the first "code fence"
+
+
+[node-glob]: https://github.com/isaacs/node-glob
+[picomatch]: https://github.com/jonschlinkert/picomatch
+[micromatch]: https://github.com/jonschlinkert/micromatch
+[so]: http://stackoverflow.com/questions/tagged/fill-range

.github/workflows/codeql.yml

@@ -0,0 +1,28 @@
+name: "CodeQL"
+
+on:
+  push:
+  pull_request:
+  schedule:
+    - cron: "0 0 * * 0"
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v2
+
+      # Initializes the CodeQL tools for scanning.
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v1
+        with:
+          languages: "javascript"
+
+      - name: Autobuild
+        uses: github/codeql-action/autobuild@v1
+
+      - name: Perform CodeQL Analysis
+        uses: github/codeql-action/analyze@v1

.github/workflows/test.yml

@@ -0,0 +1,41 @@
+name: CI
+on:
+  - push
+  - pull_request
+
+env:
+  CI: true
+  FORCE_COLOR: 2
+
+jobs:
+  run:
+    name: Node.js ${{ matrix.node }} @ ${{ matrix.os }}
+    runs-on: ${{ matrix.os }}
+
+    strategy:
+      fail-fast: false
+      matrix:
+        node: [8, 10, 12, 14, 16, 18, 20, 22]
+        os: [ubuntu-latest, windows-latest, macOS-latest]
+
+    steps:
+      - name: Clone repository
+        uses: actions/checkout@v2
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v2
+        with:
+          node-version: ${{ matrix.node }}
+
+      - name: Install npm dependencies
+        run: npm install
+
+      - name: Run tests
+        run: npm run test:ci
+
+      - name: Run Coveralls
+        # `master` should be a tag but they don't have one
+        uses: coverallsapp/github-action@master
+        if: startsWith(matrix.os, 'ubuntu') && matrix.node == 14
+        with:
+          github-token: "${{ secrets.GITHUB_TOKEN }}"

.gitignore

@@ -27,4 +27,5 @@ vendor
 temp
 tmp
 TODO.md
-package-lock.json
+package-lock.json
+*.code-*

.travis.yml

@@ -11,7 +11,7 @@ const fill70 = require('..');
  */
 
 const cycle = (e, newline) => {
-  process.stdout.write(`\u001b[G  ${e.target}${newline ? `\n` : ''}`);
+  process.stdout.write(`\u001b[G  ${e.target}${newline ? '\n' : ''}`);
 };
 
 const bench = (name, options) => {

bench/index.js

@@ -24,14 +24,19 @@
     "node": ">=8"
   },
   "scripts": {
-    "test": "mocha"
+    "lint": "eslint --cache --cache-location node_modules/.cache/.eslintcache --report-unused-disable-directives --ignore-path .gitignore .",
+    "mocha": "mocha --reporter dot",
+    "test": "npm run lint && npm run mocha",
+    "test:ci": "npm run test:cover",
+    "test:cover": "nyc npm run mocha"
   },
   "dependencies": {
     "to-regex-range": "^5.0.1"
   },
   "devDependencies": {
     "gulp-format-md": "^2.0.0",
-    "mocha": "^6.1.1"
+    "mocha": "^6.1.1",
+    "nyc": "^15.1.0"
   },
   "keywords": [
     "alpha",

package.json

@@ -1,7 +1,5 @@
 'use strict';
 
-require('mocha');
-const assert = require('assert');
 const exact = require('./support/exact');
 const fill = require('..');
 

test/custom-expand.js

@@ -1,6 +1,5 @@
 'use strict';
 
-require('mocha');
 const assert = require('assert');
 const fill = require('..');
 

test/errors.js

@@ -1,6 +1,5 @@
 'use strict';
 
-require('mocha');
 const assert = require('assert');
 const fill = require('..');