-
lnr(root, dirname, linktoDir, opts, cb) → {Object}
-
Starts at given
root
and recurses into all subdirectories. Each directory found whose name matchesdirname
is linked tolinktoDir
.Parameters:
Name Type Description root
string directory at which to start searching
dirname
string directory to link
linktoDir
string destination directory to link to
opts
Object options that allow customizing which directories are linked
Properties
Name Type Description dirFilter
function if provided only directories for which this function returns
true
are linkedcb
function called back when all directories were linked
Returns:
event emitter that emits events about the linking progress
info|verbose|warn|error
- Type
- Object
-
lnr::package(p) → {boolean}
-
A built in filter that returns
true
if the directory is considered an npm package. This is determined by ensuring that the parent directory isnode_modules
Parameters:
Name Type Description p
string full path to the directory to test
- Source:
Returns:
true
if it is a package, otherwisefalse
- Type
- boolean
Maintenance
Commit Frequency
Further analysis of the maintenance status of lnr based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.
An important project maintenance signal to consider for lnr is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.
In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.