Ask Questions and Find Answers

Hello Ivan,

thanks for your reply :-)

I also discovered that the module thows an exception on deployment:

java.lang.NullPointerException
        at com.github.yuchi.semver.Version.compareTo(Version.java:158)
        at com.github.yuchi.semver.Version.compareTo(Version.java:5)
        at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
        at java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
        at java.util.TimSort.binarySort(TimSort.java:296)
        at java.util.TimSort.sort(TimSort.java:239)
        at java.util.Arrays.sort(Arrays.java:1512)
        at java.util.ArrayList.sort(ArrayList.java:1460)
        at com.liferay.frontend.js.loader.modules.extender.internal.npm.NPMRegistryImpl._refreshJSModuleCaches(NPMRegistryImpl.java:341)
        at com.liferay.frontend.js.loader.modules.extender.internal.npm.NPMRegistryImpl._processBundle(NPMRegistryImpl.java:279)

For some reason one of the js packages inside of my module has a empty version number.

Strangely this module seems to contain my index.js (which is the main entrance point of my application), but without the version of my module.

That is because clay cannot be loaded more than once because it uses SOY under the hood and SOY uses a global namespace :-(. So, even if you use an AMD loader to attain modularity, there's a bottleneck in SOY library because every AMD module shares the same namespace.

The solution to fix this is importing clay libraries from the portal instead of providing your own. This has some limitations because you cannot control which version of clay gets loaded as you are delegating that decission to the portal itself. However, because we also use clay in the portal, chances are that it is always up to date.

If you want to import clay you need to add the following to your .npmbundlerrc file:

"config": {
    "imports": {
        "frontend-taglib-clay": {
            "clay-alert": ">=2.9.0",
            "clay-autocomplete": ">=2.9.0",
            "clay-badge": ">=2.9.0",
            "clay-button": ">=2.9.0",
            "clay-card": ">=2.9.0",
            "clay-card-grid": ">=2.9.0",
            "clay-checkbox": ">=2.9.0",
            "clay-collapse": ">=2.9.0",
            "clay-component": ">=2.9.0",
            "clay-data-provider": ">=2.9.0",
            "clay-dataset-display": ">=2.9.0",
            "clay-dropdown": ">=2.9.0",
            "clay-icon": ">=2.9.0",
            "clay-label": ">=2.9.0",
            "clay-link": ">=2.9.0",
            "clay-list": ">=2.9.0",
            "clay-loading-indicator": ">=2.9.0",
            "clay-management-toolbar": ">=2.9.0",
            "clay-modal": ">=2.9.0",
            "clay-multi-select": ">=2.9.0",
            "clay-navigation-bar": ">=2.9.0",
            "clay-pagination": ">=2.9.0",
            "clay-pagination-bar": ">=2.9.0",
            "clay-portal": ">=2.9.0",
            "clay-progress-bar": ">=2.9.0",
            "clay-radio": ">=2.9.0",
            "clay-select": ">=2.9.0",
            "clay-sticker": ">=2.9.0",
            "clay-table": ">=2.9.0",
            "clay-tooltip": ">=2.9.0"
        }
    }
}

Note that 2.9.0 should be substituted by the version you are using. It will probably make sense to have the same version you are using in package.json with a >= prepended so that if the portal updates clay your module doesn't break.

Currently, portal 7.1 is using these versions of clay -> https://github.com/liferay/liferay-portal/blob/7.1.x/modules/apps/frontend-taglib/frontend-taglib-clay/package.json

Hope this helps.

Of course, don't use a version higher than the one the portal is providing, because it won't match unless you change the semantic version expression to somehting less restricting.