0

Is there a clever way to create a module that can both be run with index.js arg1 arg2 as well as exporting itself to be used by others, ie. module.exports?

Say I have a script that kickstart a proxy server, while I can do proxy.js host port, I can't think of an easy way to export it as well. Should I look at process.argv to decide whether to exports or run itself? Or is there a better pattern?

PS: I was trying to write test cases for it but realize without module.exports, it's kinda hard to provide proper test coverage. Just curious how one would tackle this.

bitinn
  • 8,787
  • 10
  • 37
  • 64
  • `module.parent` seems like a good option, http://stackoverflow.com/questions/8864365/can-i-know-in-node-js-if-my-script-is-being-run-directly-or-being-loaded-by-an – bitinn Jan 11 '15 at 07:05
  • Closing this, it's apparent I should have split the main function into its own `proxyServer.js` module and use a wrapper `proxy.js` to provide command line function – bitinn Jan 11 '15 at 07:39
  • It's a unique question, you shouldn't close it. – laggingreflex Jan 11 '15 at 07:46

0 Answers0