NUEVA BUSQUEDA DE DATOS SRI

node_modules/chokidar/README.md

@@ -1,11 +1,9 @@
 # Chokidar [![Weekly downloads](https://img.shields.io/npm/dw/chokidar.svg)](https://github.com/paulmillr/chokidar) [![Yearly downloads](https://img.shields.io/npm/dy/chokidar.svg)](https://github.com/paulmillr/chokidar)
 
-> A neat wrapper around Node.js fs.watch / fs.watchFile / FSEvents.
+> Minimal and efficient cross-platform file watching library
 
 [![NPM](https://nodei.co/npm/chokidar.png)](https://www.npmjs.com/package/chokidar)
 
-Version 3 is out! Check out our blog post about it: [Chokidar 3: How to save 32TB of traffic every week](https://paulmillr.com/posts/chokidar-3-save-32tb-of-traffic/)
-
 ## Why?
 
 Node.js `fs.watch`:
@@ -15,6 +13,7 @@ Node.js `fs.watch`:
 * Often reports events twice.
 * Emits most changes as `rename`.
 * Does not provide an easy way to recursively watch file trees.
+* Does not support recursive watching on Linux.
 
 Node.js `fs.watchFile`:
 
@@ -35,6 +34,8 @@ Initially made for **[Brunch](https://brunch.io/)** (an ultra-swift web app buil
 and [many others](https://www.npmjs.com/browse/depended/chokidar).
 It has proven itself in production environments.
 
+Version 3 is out! Check out our blog post about it: [Chokidar 3: How to save 32TB of traffic every week](https://paulmillr.com/posts/chokidar-3-save-32tb-of-traffic/)
+
 ## How?
 
 Chokidar does still rely on the Node.js core `fs` module, but when using
@@ -46,7 +47,7 @@ On MacOS, chokidar by default uses a native extension exposing the Darwin
 implementations like `kqueue` available on most \*nix platforms. Chokidar still
 does have to do some work to normalize the events received that way as well.
 
-On other platforms, the `fs.watch`-based implementation is the default, which
+On most other platforms, the `fs.watch`-based implementation is the default, which
 avoids polling and keeps CPU usage down. Be advised that chokidar will initiate
 watchers recursively for everything within scope of the paths that have been
 specified, so be judicious about not wasting system resources by watching much
@@ -74,7 +75,7 @@ chokidar.watch('.').on('all', (event, path) => {
 ## API
 
 ```javascript
-// Example of a more typical implementation structure:
+// Example of a more typical implementation structure
 
 // Initialize watcher.
 const watcher = chokidar.watch('file, dir, glob, or array', {
@@ -114,7 +115,7 @@ watcher.add(['new-file-2', 'new-file-3', '**/other-file*']);
 var watchedPaths = watcher.getWatched();
 
 // Un-watch some files.
-watcher.unwatch('new-file*');
+await watcher.unwatch('new-file*');
 
 // Stop watching.
 // The method is async!
@@ -255,7 +256,7 @@ Additionally `all` is available which gets emitted with the underlying event
 name and path for every event other than `ready`, `raw`, and `error`.  `raw` is internal, use it carefully.
 * `.unwatch(path / paths)`: Stop watching files, directories, or glob patterns.
 Takes an array of strings or just one string.
-* `.close()`: Removes all listeners from watched files. Asynchronous, returns Promise.
+* `.close()`: **async** Removes all listeners from watched files. Asynchronous, returns Promise. Use with `await` to ensure bugs don't happen.
 * `.getWatched()`: Returns an object representing all the paths on the file
 system being watched by this `FSWatcher` instance. The object's keys are all the
 directories (using absolute paths unless the `cwd` option was used), and the
@@ -264,7 +265,7 @@ values are arrays of the names of the items contained in each directory.
 ## CLI
 
 If you need a CLI interface for your file watching, check out
-[chokidar-cli](https://github.com/kimmobrunfeldt/chokidar-cli), allowing you to
+[chokidar-cli](https://github.com/open-cli-tools/chokidar-cli), allowing you to
 execute a command on each change, or get a stdio stream of change events.
 
 ## Install Troubleshooting
@@ -286,8 +287,9 @@ execute a command on each change, or get a stdio stream of change events.
 ## Changelog
 
 For more detailed changelog, see [`full_changelog.md`](.github/full_changelog.md).
-
-- **v3.3 (Nov 2, 2019):** `FSWatcher#close()` method became async.
+- **v3.5 (Jan 6, 2021):** Support for ARM Macs with Apple Silicon. Fixes for deleted symlinks.
+- **v3.4 (Apr 26, 2020):** Support for directory-based symlinks. Fixes for macos file replacement.
+- **v3.3 (Nov 2, 2019):** `FSWatcher#close()` method became async. That fixes IO race conditions related to close method.
 - **v3.2 (Oct 1, 2019):** Improve Linux RAM usage by 50%. Race condition fixes. Windows glob fixes. Improve stability by using tight range of dependency versions.
 - **v3.1 (Sep 16, 2019):** dotfiles are no longer filtered out by default. Use `ignored` option if needed. Improve initial Linux scan time by 50%.
 - **v3 (Apr 30, 2019):** massive CPU & RAM consumption improvements; reduces deps / package size by a factor of 17x and bumps Node.js requirement to v8.16 and higher.
@@ -295,6 +297,12 @@ For more detailed changelog, see [`full_changelog.md`](.github/full_changelog.md
 - **v1 (Apr 7, 2015):** Glob support, symlink support, tons of bugfixes. Node 0.8+ is supported
 - **v0.1 (Apr 20, 2012):** Initial release, extracted from [Brunch](https://github.com/brunch/brunch/blob/9847a065aea300da99bd0753f90354cde9de1261/src/helpers.coffee#L66)
 
+## Also
+
+Why was chokidar named this way? What's the meaning behind it?
+
+>Chowkidar is a transliteration of a Hindi word meaning 'watchman, gatekeeper', चौकीदार. This ultimately comes from Sanskrit _ चतुष्क_ (crossway, quadrangle, consisting-of-four).
+
 ## License
 
 MIT (c) Paul Miller (<https://paulmillr.com>), see [LICENSE](LICENSE) file.