Allowing daemons to stop #418
                
     Open
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Couple of issues which made it very hard to stop and start an
express-pouchdbserver with active replications in defined in a_replicatordocument.replicator.js, the db variable was never set, soundefinedfordb.stopReplicatorDaemoncallAsyncRecursivetypically stops on the first daemon, since it doesn't have astopmethod, and thusfunc[0] === undefinedpouchch-replicationfire up right after the daemon gets shut down, and throw exceptions on missing db withindbData.dbswhich is empty, when trying to clean up the replication (which already has been cleaned when shutting the daemon down).Open to better ways to do this. Thank you!