Remove old broken CI tooling; run nyc as part of normal tests (#924)

* Remove old broken CI tooling; now that we've switched to GH Actions

Refs #874

* Run nyc as part of normal tests

Author: RyanZim

.travis.yml

@@ -4,11 +4,9 @@ Node.js: fs-extra
 `fs-extra` adds file system methods that aren't included in the native `fs` module and adds promise support to the `fs` methods. It also uses [`graceful-fs`](https://github.com/isaacs/node-graceful-fs) to prevent `EMFILE` errors. It should be a drop in replacement for `fs`.
 
 [![npm Package](https://img.shields.io/npm/v/fs-extra.svg)](https://www.npmjs.org/package/fs-extra)
-[![License](https://img.shields.io/npm/l/express.svg)](https://github.com/jprichardson/node-fs-extra/blob/master/LICENSE)
-[![build status](https://img.shields.io/travis/jprichardson/node-fs-extra/master.svg)](http://travis-ci.org/jprichardson/node-fs-extra)
-[![windows Build status](https://img.shields.io/appveyor/ci/jprichardson/node-fs-extra/master.svg?label=windows%20build)](https://ci.appveyor.com/project/jprichardson/node-fs-extra/branch/master)
+[![License](https://img.shields.io/npm/l/fs-extra.svg)](https://github.com/jprichardson/node-fs-extra/blob/master/LICENSE)
+[![build status](https://img.shields.io/github/workflow/status/jprichardson/node-fs-extra/Node.js%20CI/master)](https://github.com/jprichardson/node-fs-extra/actions/workflows/ci.yml?query=branch%3Amaster)
 [![downloads per month](http://img.shields.io/npm/dm/fs-extra.svg)](https://www.npmjs.org/package/fs-extra)
-[![Coverage Status](https://img.shields.io/coveralls/github/jprichardson/node-fs-extra/master.svg)](https://coveralls.io/github/jprichardson/node-fs-extra)
 [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)
 
 Why?
@@ -189,7 +187,7 @@ you're gonna have to get over it :) If `standard` is good enough for `npm`, it's
 What's needed?
 - First, take a look at existing issues. Those are probably going to be where the priority lies.
 - More tests for edge cases. Specifically on different platforms. There can never be enough tests.
-- Improve test coverage. See coveralls output for more info.
+- Improve test coverage.
 
 Note: If you make any big changes, **you should definitely file an issue for discussion first.**
 

README.md

@@ -43,7 +43,6 @@
   },
   "devDependencies": {
     "at-least-node": "^1.0.0",
-    "coveralls": "^3.0.0",
     "klaw": "^2.1.1",
     "klaw-sync": "^3.0.2",
     "minimist": "^1.1.1",
@@ -59,12 +58,9 @@
     "!lib/**/__tests__/"
   ],
   "scripts": {
-    "full-ci": "npm run lint && npm run coverage",
-    "coverage": "nyc -r lcovonly npm run unit",
-    "coveralls": "coveralls < coverage/lcov.info",
     "lint": "standard",
     "test-find": "find ./lib/**/__tests__ -name *.test.js | xargs mocha",
     "test": "npm run lint && npm run unit",
-    "unit": "node test.js"
+    "unit": "nyc node test.js"
   }
 }