• Tue 2018.09.24

    cont.

    While I re-attempt the above, too limited a time during week, I have a similar issue with establishing a class reference in a deployed module.

    Do I need the similar 'added C' as in 'exports.C = C;' to reference a class definition or do I need the constructor function to be part of the module? Is it bad practice to reference that class without the constructor function as part of the module?
    ( even though the constructor is defined inside the class definition )

    I've just been using exports = ClassName; which seems to be working fine. var cnInst = new ClassName();

    Is that above mentioned syntax the solution to referencing multiple classes within the same module? e.g. can more than one class exist in any one module?
    exports.ClassName = ClassName;
    exports.ClassNameDiff = ClassNameDiff;


    EDIT
    Ahhhh, . . . I think the solution is the last code block from #3 above. After

    'Now you can use it like:'

About

Avatar for Robin @Robin started