.github/workflows/ci.yml

@@ -0,0 +1,22 @@
+name: CI
+
+on: [push, pull_request]
+
+jobs:
+    test:
+        name: Tests
+        strategy:
+            matrix:
+                node: [8.x, 10.x, 12.x, 14.x, 15.x]
+        runs-on: ubuntu-latest
+        steps:
+            - name: Checkout sources
+              uses: actions/checkout@v2
+            - name: Install Node.js ${{matrix.node}}
+              uses: actions/setup-node@v2-beta
+              with:
+                  node-version: ${{matrix.node}}
+            - name: Install dependencies
+              run: npm install
+            - name: npm test
+              run: npm test

.npmrc

@@ -0,0 +1 @@
+package-lock=false

CHANGELOG.md

@@ -0,0 +1,8 @@
+# watchify Change Log
+All notable changes to this project will be documented in this file.
+This project adheres to [Semantic Versioning](http://semver.org/).
+
+## 4.0.0
+* Update dependencies.
+
+This release drops support for Node.js versions older than 8.10, following the upgrade to `chokidar` 3.x.

package.json

@@ -1,23 +1,26 @@
 {
   "name": "watchify",
-  "version": "3.11.1",
+  "version": "4.0.0",
   "description": "watch mode for browserify builds",
   "main": "index.js",
   "bin": "bin/cmd.js",
+  "engines": {
+    "node": ">= 8.10.0"
+  },
   "dependencies": {
-    "anymatch": "^2.0.0",
-    "browserify": "^16.1.0",
-    "chokidar": "^2.1.1",
+    "anymatch": "^3.1.0",
+    "browserify": "^17.0.0",
+    "chokidar": "^3.4.0",
     "defined": "^1.0.0",
     "outpipe": "^1.1.0",
-    "through2": "^2.0.0",
-    "xtend": "^4.0.0"
+    "through2": "^4.0.2",
+    "xtend": "^4.0.2"
   },
   "devDependencies": {
     "brfs": "^2.0.1",
-    "mkdirp": "~0.5.1",
+    "mkdirp": "^0.5.5",
     "split": "^1.0.0",
-    "tape": "^4.2.2",
+    "tape": "^5.1.1",
     "uglify-js": "^2.5.0",
     "win-spawn": "^2.0.0"
   },
@@ -26,9 +29,9 @@
   },
   "repository": {
     "type": "git",
-    "url": "git://github.com/substack/watchify.git"
+    "url": "git://github.com/browserify/watchify.git"
   },
-  "homepage": "https://github.com/substack/watchify",
+  "homepage": "https://github.com/browserify/watchify",
   "keywords": [
     "browserify",
     "browserify-tool",

readme.markdown

@@ -2,7 +2,7 @@
 
 watch mode for [browserify](https://github.com/substack/node-browserify) builds
 
-[![build status](https://secure.travis-ci.org/substack/watchify.svg?branch=master)](http://travis-ci.org/substack/watchify)
+[![build status](https://secure.travis-ci.org/browserify/watchify.svg?branch=master)](http://travis-ci.org/browserify/watchify)
 
 Update any source file and your browserify bundle will be recompiled on the
 spot.
@@ -90,7 +90,7 @@ var watchify = require('watchify');
 
 ## watchify(b, opts)
 
-watchify is a browserify [plugin](https://github.com/substack/node-browserify#bpluginplugin-opts), so it can be applied like any other plugin.
+watchify is a browserify [plugin](https://github.com/browserify/browserify#bpluginplugin-opts), so it can be applied like any other plugin.
 However, when creating the browserify instance `b`, **you MUST set the `cache`
 and `packageCache` properties**:
 
@@ -107,7 +107,7 @@ var b = browserify({
 });
 ```
 
-**By default, watchify doesn't display any output, see [events](https://github.com/substack/watchify#events) for more info.**
+**By default, watchify doesn't display any output, see [events](https://github.com/browserify/watchify#events) for more info.**
 
 `b` continues to behave like a browserify instance except that it caches file
 contents and emits an `'update'` event when a file changes. You should call
@@ -240,7 +240,7 @@ to get just the library.
 
 ## rebuilds on OS X never trigger
 
-It may be related to a bug in `fsevents` (see [#250](https://github.com/substack/watchify/issues/205#issuecomment-98672850)
+It may be related to a bug in `fsevents` (see [#250](https://github.com/browserify/watchify/issues/205#issuecomment-98672850)
 and [stackoverflow](http://stackoverflow.com/questions/26708205/webpack-watch-isnt-compiling-changed-files/28610124#28610124)).
 Try the `--poll` flag
 and/or renaming the project's directory - that might help.