Single Entry Point for an Extension

Single Entry Point for an Extension

Single Entry Point for an Extension

If you created the files and folders described in Folder Structure, you can walk through this example to see how a single entry point works.

In the extension's manifest.json file, add the path to the ModuleOne.js file as the entry point for each application your extension will be applied to. For example, if your extension only applies to the checkout application, set the entry point as shown in the following example:

"javascript": {
        "entry_points": {
            "shopping": "Modules/ModuleOne/JavaScript/ModuleOne.js"

Now if you run the gulp command to update the extension manifest:

gulp extension:update-manifest

And then run a local test of your extension with this gulp command:

gulp extension:local

When you access your local site and check your browser's developer console, you see this message:

ModuleOne loaded!

This result is expected because, although the extension's manifest file has been updated and includes the ModuleTwo file in its list of files, you have not called the second module.

When your extension is loaded, only the entry point file in the manifest is called. Therefore, if you want additional code to be called, you need to add calls to that entry point file's mountToApp() method. To learn more, see Calling Files in Other Modules.