Wrapper around fs.watch that falls back to fs.watchFile
Installations
npm install filewatcher
Score
99.3
Supply Chain
96.8
Quality
75.5
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Developer
fgnass
Developer Guide
Module System
CommonJS
Min. Node Version
Typescript Support
No
Node Version
6.2.1
NPM Version
3.9.3
Statistics
54 Stars
42 Commits
8 Forks
3 Watching
2 Branches
2 Contributors
Updated on 23 Oct 2023
Bundle Size
1.96 kB
Minified
871.00 B
Minified + Gzipped
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
31,011,656
Last day
-15.3%
20,046
Compared to previous day
Last week
-3.3%
111,840
Compared to previous week
Last month
27.2%
436,173
Compared to previous month
Last year
-2.6%
4,419,341
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
filewatcher
Simple wrapper around fs.watch
that works around the various issues
you have to deal with when using the Node API directly.
More precisely filewatcher …
- always reports file names (for all events on all OSes)
- works well with editors that perform atomic writes (save & rename) like Sublime Text or vim
- doesn't fire twice when files are saved
- falls back to
fs.watchFile
when running out of file handles - has no native dependencies
- uses Node's async APIs under the hood
This module is used by node-dev and instant.
Usage
1var filewatcher = require('filewatcher'); 2 3var watcher = filewatcher(); 4 5// watch a file 6watcher.add(__filename); 7 8// ... or a directory 9watcher.add(__dirname); 10 11watcher.on('change', function(file, stat) { 12 console.log('File modified: %s', file); 13 if (!stat) console.log('deleted'); 14});
To stop watching, you can remove either a single file or all watched files at once:
1watcher.remove(file) 2watcher.removeAll()
Notify users when falling back to polling
When the process runs out of file handles, filewatcher closes all watchers and transparently switches to fs.watchFile
polling. You can notify your users by listening to the fallback
event:
1watcher.on('fallback', function(limit) { 2 console.log('Ran out of file handles after watching %s files.', limit); 3 console.log('Falling back to polling which uses more CPU.'); 4 console.log('Run ulimit -n 10000 to increase the limit for open files.'); 5});
Options
You can pass options to filewatcher()
in order to tweak its internal settings. These are the defaults:
1// the default options 2var opts = { 3 forcePolling: false, // try event-based watching first 4 debounce: 10, // debounce events in non-polling mode by 10ms 5 interval: 1000, // if we need to poll, do it every 1000ms 6 persistent: true // don't end the process while files are watched 7}; 8 9var watcher = filewatcher(opts)
The MIT License (MIT)
Copyright (c) 2013-2016 Felix Gnass
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
Found 1/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
license file not detected
Details
- Warn: project does not have a license file
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 1 are checked with a SAST tool
Score
2.6
/10
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More