Research
Security News
Malicious npm Packages Inject SSH Backdoors via Typosquatted Libraries
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
This is a fork of the official version 3.0.x
branch. Sass need to support older
versions of ruby than Guard wants to support on an ongoing basis, so we are releasing
updates as needed for critical fixes and will support ruby 2.0 and
greater for as long as Sass users need it. Our blog has more information about
ths Ruby version policy for Sass.
The Listen gem listens to file modifications and notifies you about the changes.
listen
gem to version '~> 2.10'
.Pull requests or help is very welcome for these.
The simplest way to install Listen is to use Bundler.
gem 'listen', '~> 3.0' # NOTE: for TCP functionality, use '~> 2.10' for now
Call Listen.to
with either a single directory or multiple directories, then define the "changes" callback in a block.
listener = Listen.to('dir/to/listen', 'dir/to/listen2') do |modified, added, removed|
puts "modified absolute path: #{modified}"
puts "added absolute path: #{added}"
puts "removed absolute path: #{removed}"
end
listener.start # not blocking
sleep
Listeners can also be easily paused/unpaused:
listener = Listen.to('dir/path/to/listen') { |modified, added, removed| puts 'handle changes here...' }
listener.start
listener.paused? # => false
listener.processing? # => true
listener.pause # stops processing changes (but keeps on collecting them)
listener.paused? # => true
listener.processing? # => false
listener.unpause # resumes processing changes ("start" would do the same)
listener.stop # stop both listening to changes and processing them
Note: While paused, Listen keeps on collecting changes in the background - to clear them, call "stop"
Note: You should keep track of all started listeners and stop them properly on finish.
Listen ignores some directories and extensions by default (See DEFAULT_IGNORED_DIRECTORIES and DEFAULT_IGNORED_EXTENSIONS in Listen::Silencer), you can add ignoring patterns with the ignore
option/method or overwrite default with ignore!
option/method.
listener = Listen.to('dir/path/to/listen', ignore: /\.txt/) { |modified, added, removed| # ... }
listener.start
listener.ignore! /\.pkg/ # overwrite all patterns and only ignore pkg extension.
listener.ignore /\.rb/ # ignore rb extension in addition of pkg.
sleep
Note: :ignore
regexp patterns are evaluated against relative paths.
Note: Ignoring paths does not improve performance, except when Polling (#274)
Listen catches all files (less the ignored ones) by default. If you want to only listen to a specific type of file (i.e., just .rb
extension), you should use the only
option/method.
listener = Listen.to('dir/path/to/listen', only: /\.rb$/) { |modified, added, removed| # ... }
listener.start
listener.only /_spec\.rb$/ # overwrite all existing only patterns.
sleep
Note: :only
regexp patterns are evaluated only against relative file paths.
Changes to the listened-to directories gets reported back to the user in a callback.
The registered callback gets invoked, when there are changes, with three parameters:
modified
, added
and removed
paths, in that particular order.
Paths are always returned in their absolute form.
Example:
listener = Listen.to('path/to/app') do |modified, added, removed|
# This block will be called when there are changes.
end
listener.start
sleep
or ...
# Create a callback
callback = Proc.new do |modified, added, removed|
# This proc will be called when there are changes.
end
listener = Listen.to('dir', &callback)
listener.start
sleep
All the following options can be set through the Listen.to
after the directory path(s) params.
ignore: [%r{/foo/bar}, /\.pid$/, /\.coffee$/] # Ignore a list of paths
# default: See DEFAULT_IGNORED_DIRECTORIES and DEFAULT_IGNORED_EXTENSIONS in Listen::Silencer
ignore!: %r{/foo/bar} # Same as ignore options, but overwrite default ignored paths.
only: %r{.rb$} # Only listen to specific files
# default: none
latency: 0.5 # Set the delay (**in seconds**) between checking for changes
# default: 0.25 sec (1.0 sec for polling)
wait_for_delay: 4 # Set the delay (**in seconds**) between calls to the callback when changes exist
# default: 0.10 sec
force_polling: true # Force the use of the polling adapter
# default: none
relative: false # Whether changes should be relative to current dir or not
# default: false
polling_fallback_message: 'custom message' # Set a custom polling fallback message (or disable it with false)
# default: "Listen will be polling for changes. Learn more at https://github.com/guard/listen#listen-adapters."
Setting the environment variable LISTEN_GEM_DEBUGGING=1
sets up the INFO level logger, while LISTEN_GEM_DEBUGGING=2
sets up the DEBUG level logger.
You can also set Listen.logger
to a custom logger.
The Listen gem has a set of adapters to notify it when there are changes.
There are 4 OS-specific adapters to support Darwin, Linux, *BSD and Windows. These adapters are fast as they use some system-calls to implement the notifying function.
There is also a polling adapter - although it's much slower than other adapters, it works on every platform/system and scenario (including network filesystems such as VM shared folders).
The Darwin and Linux adapters are dependencies of the Listen gem so they work out of the box. For other adapters a specific gem will have to be added to your Gemfile, please read below.
The Listen gem will choose the best adapter automatically, if present. If you
want to force the use of the polling adapter, use the :force_polling
option
while initializing the listener.
If you are on Windows, it's recommended to use the wdm
adapter instead of polling.
Please add the following to your Gemfile:
gem 'wdm', '>= 0.1.0' if Gem.win_platform?
If you are on *BSD you can try to use the rb-kqueue
adapter instead of polling.
Please add the following to your Gemfile:
require 'rbconfig'
if RbConfig::CONFIG['target_os'] =~ /bsd|dragonfly/i
gem 'rb-kqueue', '>= 0.2'
end
Please visit the installation section of the Listen WIKI for more information and options for potential fixes.
NOTE: without providing the output after setting the LISTEN_GEM_DEBUGGING=1
environment variable, it can be almost impossible to guess why listen is not working as expected.
See TROUBLESHOOTING
If Listen seems slow or unresponsive, make sure you're not using the Polling adapter (you should see a warning upon startup if you are).
Also, if the directories you're watching contain many files, make sure you're:
:ignore
and :only
options to avoid tracking directories you don't care about (important with Polling and on MacOS):latency
and :wait_for_delay
options not too small or too big (depends on needs)When in doubt, LISTEN_GEM_DEBUGGING=2 can help discover the actual events and time they happened.
See also Tips and Techniques.
Pull requests are very welcome! Please try to follow these simple rules if applicable:
For questions please join us in our Google group or on
#guard
(irc.freenode.net).
Thibaud Guillaume-Gentil (@thibaudgg)
FAQs
Unknown package
We found that sass-listen demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.