Edit Question - KnowledgeHub

Title Body

I am playing around and learning about vows with a personal project. This is a small client side library, with testing done in vows. Therefore, I must build and test a file that is written like this: (function(exports) { var module = export.module = { "version":"0.0.1" }; //more stuff })(this); In my testing (based off of science.js , d3, etc.) requires that module like so: require("../module"); I continued to get a "module not defined error" when trying to run the tests, so I went to a repl and ran: require("../module") and it returned: { module: { version: "0.0.1" } } I realize I could do something like: var module = require("../module").module; but feel like I am creating a problem by doing it that way, especially since the libraries that I based this project on are doing it in the format I described. I would like for my project to behave similar to those which I based it off of, where: require("../module"); creates a variable in this namespace: module.version; //is valid. I have seen this in a variety of libraries, and I am following the format and thought process to the T but believe I might be missing something about require behavior I don't know about.

Tags (comma-separated) Cancel