		{
		"name": "chokidar",
		"description": "A neat wrapper around node.js fs.watch / fs.watchFile / fsevents.",
		"version": "0.11.1",
		"version": "0.12.0",
		"keywords": [
		@@ -32,4 +32,5 @@ "fs",
		},
		"main": "lib",
		"files": [
		"index.js"
		"lib"
		],
		@@ -46,5 +47,5 @@ "devDependencies": {
		"dependencies": {
		"readdirp": "~1.1.0",
		"readdirp": "~1.2.0",
		"async-each": "~0.1.5"
		}
		}

README.md

		@@ -59,2 +59,3 @@ # Chokidar
		.on('ready', function() {console.info('Initial scan complete. Ready for changes.')})
		.on('raw', function(event, path, details) {console.info('Raw event info:', event, path, details)})

		@@ -88,6 +89,8 @@ // 'add', 'addDir' and 'change' events also receive stat() results as second argument.
		object of that path).
		* `options.persistent` (default: `false`). Indicates whether the process
		should continue to run as long as files are being watched.
		* `options.persistent` (default: `true`). Indicates whether the process
		should continue to run as long as files are being watched. If set to
		`false` when using `fsevents` to watch, no more events will be emitted
		after `ready`, even if the process continues to run.
		* `options.ignorePermissionErrors` (default: `false`). Indicates
		whether to watch files that don't have read permissions.
		whether to watch files that don't have read permissions.
		* `options.ignoreInitial` (default: `false`). Indicates whether chokidar
		@@ -98,7 +101,16 @@ should ignore the initial `add` events or not.
		polling for binary files (see extensions in src/is-binary).
		* `options.useFsEvents` (default: `true` on OS X). Whether to use the `fsevents` watching interface if
		available. When `true` and `fsevents` is available, it supercedes the `usePolling` setting.
		* `options.usePolling` (default: `false` on Windows, `true` on Linux and OS X). Whether to use fs.watchFile
		(backed by polling), or fs.watch. If polling leads to high CPU utilization,
		consider setting this to `false`.
		* `options.useFsEvents` (default: `true` on OS X). Whether to use the
		`fsevents` watching interface if available. When set to `true` and
		`fsevents` is available this supercedes the `usePolling` setting.
		* `options.usePolling` (default: `false` on Windows, `true` on Linux and OS X).
		Whether to use fs.watchFile (backed by polling), or fs.watch. If polling
		leads to high CPU utilization, consider setting this to `false`. Polling
		may be necessary to successfully watch files in certain situation, such as
		network mounted drives.
		* `options.followSymlinks` (default: `true`). When `false`, only the
		symlinks themselves will be watched for changes instead of following
		the link references and bubbling events through the link's path.
		* `options.atomic` (default: `true` if `useFsEvents` and `usePolling` are `false`).
		Automatically filters out artifacts that occur when using editors that use
		"atomic writes" instead of writing directly to the source file.

		@@ -110,5 +122,5 @@ `chokidar.watch()` produces an instance of `FSWatcher`. Methods of `FSWatcher`:
		* `.on(event, callback)`: Listen for an FS event.
		Available events: `add`, `addDir`, `change`, `unlink`, `unlinkDir`, `ready`, `error`.
		Available events: `add`, `addDir`, `change`, `unlink`, `unlinkDir`, `ready`, `raw`, `error`.
		Additionally `all` is available which gets emitted with the underlying event name
		and path for every event other than `ready` and `error`.
		and path for every event other than `ready`, `raw`, and `error`.
		* `.close()`: Removes all listeners from watched files.
		@@ -115,0 +127,0 @@

index.js

chokidar - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics

Worsened metrics

Dependency changes