-
mothership(start, ismothership, cb)
-
Searches upwards from start for package.json files, asking for each if it is the mothership. If a mothership is found it calls back with that. If it reaches the top of the univers it calls back with nothing.
mothership result
path
: full path to thepackage.json
that is the mother shippack
: thepackage.json
object, same that was passed to ismothership
Parameters:
Name Type Description start
string full path at which to start looking for the mothership
ismothership
function invoked with the package object, needs to return true if it is the mothership
cb
function called back with either an error or full path to package.json that is the mothership
-
mothership::sync(start, ismothership) → {string}
-
Synchronous version of mothership.
Parameters:
Name Type Description start
string full path at which to start looking for the mothership
ismothership
function invoked with the package object, needs to return true if it is the mothership
Returns:
full path to package.json that is the mothership or
null
if it wasn't found- Type
- string
Maintenance
Commit Frequency
Further analysis of the maintenance status of mothership 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 mothership 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.