I mean, technically you could declare the functions you wanted as variables and then inject them into the module functions that would use them, but that's kind of an anti-pattern in Javascript.

...Which is kind of funny if you're used to a language like C#, where constructor/dependency injection is all the rage. However, there are pros and cons to each approach. If you require the npm module in your module, you're tightly coupled to that module. If you inject the particular function into your module, you aren't tightly coupled, and you can change what function is called at will, based on what you injected. This could make your code more testable.

Some frameworks like Angular have DI systems built in, or you can Google "npm dependency injection" if this sounds like something you need.