But then, at that point, we could just do this:
Although that’s much less convenient for less technical users who may not want (or know how) to setup an npm package.
I think we’ll try this approach for our libs 
, and just pass the Pipedream app (Slack, etc.) as a parameter when necessary.
Less convenient & a bit more work… but it will work. 
And the package will have to be public, but that’s fine as the code itself will be pretty generic. No secret sauce, business logic, or credentials in there. 
It’s somewhat de-coupling users from Pipedream though… which can be a good or bad thing, depending on the perspective.