async-waterfall | isolated async waterfall module for JavaScript | Reactive Programming library

Based on the answer here, which has async waterfall based on a condition inside another parent waterfall.

How would the arguments passing work while passing arguments to the function(condition, callback){} in the following.

I'm planning on using a set of a little bit more sophisticated conventions to import assets in my webpack project. So I'm trying to write a plugin that should rewrite parts of requested module locators and then pass that down the resolver waterfall.

Let's assume we just want to

• check if a requested module starts with the # character and
• if so, replace that with ./lib/. The new module locator should now be looked up by the default resolver.

This means when a file /var/www/source.js does require("#example"), it should then actually get /var/www/lib/example.js.

So far I've figured out I'm apparently supposed to use the module event hook for this purpose. That's also the way chosen by other answers which unfortunately did not help me too much.

So this is my take on the custom resolve plugin, it's pretty straightforward:

I have a following object in my node,js module, named data:

I know this is a topic that has been brought up here before, but I'm using async.waterfall with rethinkdb and I'm getting Error: Callback was already called. The odd part is that even though it throws that error and crashes the app, it still will create the database and tables I need. I have read a few other post with answers like NodeJS Async: Callback already called? or Using async.waterfall, but I can't seem to get anywhere. My console also tells me the error is at db.js:40:9, but I'm new to Node and just not sure what it wants with the callbacks. What am I doing wrong? Do I need to nest my callbacks here? The code I am using is posted below. Any help I can get here is greatly appreciated and if need be I can post other relevant code. Thanks guys.

db.js: