Chris E
Chris E

Reputation: 59

Creating an instance of multiple javascript modules

This related to javascript code. My application has many sub applications that are sometimes used more then once on a page. An example would be an application that allows the user to search for some data and displaying the search results. This application my be used in multiple places on a page to search for different types of data. Each sub application typically includes many javascript modules each in a separate file. I have experienced with many different module patterns to try to create a separate instance of multiple modules/files but with no success. There is much advice online how to create multiple instances of objects, using factory pattern etc but I have not been able to make it work with the name space structure and module pattern my application. See example below.

The question is how can you create multiple independent instances of SubAppA including all its sub modules.

(New file)

var MainApp     = MainApp || {};
MainApp.SubAppA = MainApp.SubAppA || {};

MainApp.SubAppA.Config = (function () {
    
    function A () { ... };
    function B () { ... };
    
    return {
        A : A,
        B : B
    }
})();

(New file)

var MainApp     = MainApp || {};
MainApp.SubAppA = MainApp.SubAppA || {};

MainApp.SubAppA.GetData = (function () {
    
    function A () { ... };
    function B () { ... };
    
    return {
        A : A,
        B : B
    }
})();

(New file)

var MainApp     = MainApp || {};
MainApp.SubAppA = MainApp.SubAppA || {};

MainApp.SubAppA.DisplayData = (function () {
    
    etc.....

Many thanks in advance

--- Additional information after solution proposed by MikeM -----

Thanks MikeM, you answer gave me a better understanding but when trying to implement it using my existing name space structure, I can't get the modules to communicate with each other. I tried the following:

//Solution $S.AS - New file
var $S  = $S || {};
$S.AS   = $S.AS || {};

$S.AS.DataStore = function () {
    var _SomeVar    = "Default";
    
    function SetVar (Data) {
        _SomeVar = Data;
    };
    function GetVar () {
        return _SomeVar;
    };
    
    return {
        SetVar : SetVar,
        GetVar : GetVar
    }
};

//Solution $S.AS - New file
var $S  = $S || {};
$S.AS   = $S.AS || {};

$S.AS.ManageData = function () {
    
    function StoreData (Data) {
        console.log($S.AS.DataStore);  //outputs f ()
        //Does now work since DataStore is now a function
        //$S.AS.DataStore.SetVar(Data);  
        $S.AS.DataStore().SetVar(Data);  
    };
    
    function DisplayData () {  
        //Does now work since DataStore is now a function
        //var SomeVar = $S.AS.DataStore.GetVar();  
        //Does not work, still outputs "Default"
        var SomeVar = $S.AS.DataStore().GetVar();
        console.log(SomeVar);
    };
    
    return {
        StoreData : StoreData,
        DisplayData : DisplayData
    }
};

//Solution $S.AS - New file - The contructor function for AS
var MainApp     = MainApp || {};
MainApp.S       = MainApp.S || {};
MainApp.S.AS    = MainApp.S.AS || {};

MainApp.S.AS = function () {
    
    this.DataStore      = $S.AS.DataStore();
    this.ManageData     = $S.AS.ManageData();
    //additional modules
    
};

//Main/Page specific code - creating the different instances
MainApp.S.AS_1 = new MainApp.S.AS();
MainApp.S.AS_2 = new MainApp.S.AS();

//Attemps to store and retrieve data

//Stores AAA in the DataStore module
MainApp.S.AS_1.ManageData.StoreData("AAA");
//Stores BBB in the DataStore module
MainApp.S.AS_2.ManageData.StoreData("BBB");
//Not working, ouputs: "Default" (Desired result is "AAA")
MainApp.S.AS_1.ManageData.DisplayData();
//Not working, ouputs: "Default" (Desired result is "BBB");
MainApp.S.AS_2.ManageData.DisplayData();

I think I understand why "Default" is output (the call is made to the original variable stored at page load) but not how to fix it.
For context, I have a custom php script that concatenates all the JS files required for a page and then adds them as a single tag to the page. I thought this would speed up script loading, in particular since most of my pages will have 50+ JS files/modules. A typical Name space structure for a page will look as follows (but with a lot more modules):

MainApp = {
    //Page specific or utility modules
    ModuleA : [ func / module ],
    ModuleB : [ func / module ],
    ModuleC : [ func / module ],
    ModuleD : [ func / module ],
    //Resulable applications consisting of multiple modules
    SubAppA : {
        ModuleA : [ func / module ],
        ModuleB : [ func / module ],
        ModuleC : [ func / module ],
        ModuleD : [ func / module ],
    },
    SubAppB : {
        ModuleA : [ func / module ],
        ModuleB : [ func / module ],
        ModuleC : [ func / module ],
        ModuleD : [ func / module ],
    }
}

I was hoping that I can somehow preserver this structure to avoid the risk of conflicting module names. I am happy to change the structure of the modules themselves (e.g. from IIFE to something else) to get an solution to the question. Thanks

Upvotes: 1

Views: 1275

Answers (2)

Chris E
Chris E

Reputation: 59

Thanks MikeM, it is now working, very helpful! Yes I am aware of that I need to look at ES modules closer. I learned to code recently to test an idea after working in a completely different field for 17 years so some shortcuts had to be made ...

Here is a write up of my implementation step by step in case it helps someone else that is not too familiar with Javascript modules.

The objectives of the question were to:

  • Enable multiple instances of an application to exist on a page where each application consists of multiple modules
  • Enable the modules to call methods in other modules
  • Make it easy to instantiate (create a new version) of the application

Some things to consider in relation to below solution:

  • Rather than static calls to methods in other module (e.g. ReuseApp.App1.Display.DisplayData(Data) each module stores an internal reference of the top object of the newly created instance of the application (e.g. _App.Display.DisplayData(Data).
  • Module are created without the immediately evoked feature (i.e. no IIFE pattern).
  • A construction function referencing all required module are required. This function will send the newly created object (this) into each module e.g. this.Config = ReuseApps.App1.Config(this);
  • Each module to take this reference as a parameter (App) and store it within the module (_App). _App will be used when calling other module methods.

Step by step by step guide:

STEP A: Create modules using the following pattern (disregard multi level namespaces if not needed):

//Separate file e.g. Config.js
const ReuseApps = ReuseApps || {};
ReuseApps.App1 = ReuseApps.App1 || {};

ReuseApps.App1.Config = function (App) {
   let  _App;  //Used to call other module methods
   let _Settings = {};
   function Init (Settings) {
      _Settings = Settings;
      //Configure app e.g. store element refs, add event handlers etc
      var Data = GetDataFromSomeWhere();
      //Call another module using the _App reference
      _App.Display.DisplayData(Data);
   }
   _App = App;
   Return {
      Init : Init
   }
}

//Separate file e.g. Display.js
const ReuseApps = ReuseApps || {};
ReuseApps.App1 = ReuseApps.App1 || {};

ReuseApps.App1.Display = function (App) {
    let _App;  //Used to call other module methods
    function DisplayData (Data) {
       //Display Data in DOM
   }
   _App = App;
   return {
      DisplayData : DisplayData
   }
}

STEP B: Create the construction function required to create a new instance of application

//can be in separate file e.g. app1_create.js
function App1Create () {
   this.Config = ReuseApps.App1.Config(this);
   this.Display = ReuseApps.App1.Display(this);
   //etc more modules …
}

STEP C: Creating a separate instance of above application in the main code

//Create new instance using constructur function
//(Assumes the MainApp namespace exists already)
MainApp.ViewDataList = new App1Create();
//If application needs to be initiated
var Settings = { some settings };
MainApp.ViewDataList.Config.Init(Settings);

Upvotes: 1

MikeM
MikeM

Reputation: 13641

A simple example of one way of creating "multiple independent instances of SubAppA including all its sub modules", where the modules are defined in multiple files:

// test.js
import { MainApp } from './mainApp.js';
import { SubApp } from './subApp.js';

MainApp.SubAppA = new SubApp();
console.log(MainApp.SubAppA.Config.A());    // 1

MainApp.SubAppB = new SubApp();
console.log(MainApp.SubAppB.Config.B());    // -1


// subApp.js
import { config } from './config.js';
import { getData } from './getData.js';

export function SubApp() {
  this.Config = config();
  this.GetData = getData();
}


// config.js
export function config() {
  let counter = 0;
  function A() { return ++counter };
  function B() { return --counter };
  return {
    A: A,
    B: B
  }
}

As a single file:

const MainApp = {};

function SubApp() {
  this.Config = config();
  this.GetData = getData();
}

function config() {
  let counter = 0;
  function A() { return ++counter };
  function B() { return --counter };
  return {
    A: A,
    B: B
  }
}

function getData() {
  let counter = 0;
  function A() { return ++counter };
  function B() { return --counter };
  return {
    A: A,
    B: B
  }
}

MainApp.SubAppA = new SubApp();
console.log(MainApp.SubAppA.Config.A());    // 1
console.log(MainApp.SubAppA.GetData.A());   // 1
console.log(MainApp.SubAppA.Config.B());    // 0

MainApp.SubAppB = new SubApp();
console.log(MainApp.SubAppB.Config.B());    // -1
console.log(MainApp.SubAppB.GetData.B());   // -1
console.log(MainApp.SubAppB.Config.A());    // 0
       

The important difference with your own code is that I have replaced the Immediately-Invoked Function Expressions (IIFE) with normal functions that create closures every time a SubApp is created.

Added in response to your edit:

For the code you added in your edit to work, you need to make sure that you pass a reference to the parent object when you create a new ManageData object:

$S.AS.ManageData = function (owner) {

    function StoreData (Data) {  
        owner.DataStore.SetVar(Data);  
    };
    
    function DisplayData () {  
        var SomeVar = owner.DataStore.GetVar();
        console.log(SomeVar);
    };
    
    return {
        StoreData : StoreData,
        DisplayData : DisplayData
    }
};

// ...

MainApp.S.AS = function () {    
    this.DataStore      = $S.AS.DataStore();
    this.ManageData     = $S.AS.ManageData(this);  
};

I encourage you to use ES modules to structure your code and avoid naming collisions. A single file can be created from a module bundler such as roll-up.js.

Upvotes: 0

Related Questions