exposed your modules
package.json file, you can use them in your portlets. The
require attribute makes it easy.
This tutorial covers how to access your exposed modules in your portlets. Follow the steps below to use your exposed modules in your portlets.
auitaglib in your view JSP:
<%@ taglib uri="http://liferay.com/tld/aui" prefix="aui" %>
Note: if you created the portlet using Blade, the
auitaglib is already provided for you in the
aui:scripttag to the JSP and set the
requireattribute to the relative path for your module.
requireattribute lets you include your exposed modules in your JSP. The AMD Loader fetches the specified module and its dependencies. An example faux Console Logger Portlet’s
view.jspshown below includes the module
<aui:script require="js-logger/logger.es"> var Logger = jsLoggerLoggerEs.default; var loggerOne = new Logger('*** -> '); loggerOne.log('Hello'); var loggerDefault = new Logger(); loggerDefault.log('World'); </aui:script>
References to the module within the script tag are named after the
requirevalue, in camel-case and with all invalid characters removed. The
jsLoggerLoggerEsis derived from the module’s relative path value
js-logger/logger.es. The value is stripped of its dash and slash characters and converted to camel case.
Thanks to the
aui:script tag and its
require attribute, using your modules
in your portlet is a piece of cake!