Liferay JS Portlet Extender / js_loader_modules / Angular https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=112006611 2026-04-04T14:20:53Z 2026-04-04T14:20:53Z Iván Zaera Avellón https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=112014466 2019-01-15T07:46:28Z 2019-01-15T07:46:28Z

<p>Hi Armando:</p> <p> </p> <p>1) We need to release version 1.1.0 of the extender. Meanwhile, generate your projects without settings configuration support which is the culprit of the need for 1.1.0 (see <a href="https://github.com/liferay/liferay-npm-build-tools/wiki/.npmbundlerrc-file-reference#create-jarfeaturesjs-extender">this link</a> on how the bundler decides which version to require).</p> <p> </p> <p>2) We are already working in a big change in the loader to avoid the need for the js_loader_modules file. All module resolutions will take place in the server so that the loader doesn't need to know anything about the modules that are installed in the served. However, that will take time and may not be available in older versions of the portal so, in the meantime, we recommend to activate the GZipFilter so that the js_loader_modules is compressed (it will be highly compressed because it's mainly redundant text). That should make the trick until the other feature arrives.</p> <p> </p> <p>Hope that helps :-),</p> <p>Ivan</p>

Iván Zaera Avellón 2019-01-15T07:46:28Z Armando Del Rosario https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=112006610 2019-01-14T18:30:38Z 2019-01-14T18:30:38Z

<p>Hi all...</p> <p>Im trying to follow the Angular Deduplication examples and got a few questions....</p> <p> </p> <p> <u> <strong> <em>Case 1:</em></strong></u></p> <p> </p> <p> <strong>The Context:</strong></p> <p>Using the yeoman <a href="https://www.npmjs.com/package/generator-liferay-bundle">generator-liferay-bundle</a>, create two angular portlet with deduplication mode (Shared packages bundle a.k.a. provider &amp; Angular based portlet a.k.a consumer).</p> <p> </p> <p>The consumer portlet don't start because it ask for osgi com.liferay.frontend.js.portlet.extender@1.1.0</p> <p> </p> <p>There is a <a href="https://web.liferay.com/es/marketplace/-/mp/application/115543020">Liferay JS Portlet Extender</a> 1.0.0 in LPKG file at the marketplace (inside it, is the 1.0.5) <img alt="surprise" height="23" src="https://community.liferay.com/o/frontend-editor-ckeditor-web/ckeditor/plugins/smiley/images/omg_smile.png" title="surprise" width="23" /></p> <p>At the <a href="https://mvnrepository.com/artifact/com.liferay/com.liferay.frontend.js.portlet.extender/1.0.6">maven repo its the 1.0.6</a>, so i downloaded and installed that one</p> <p> </p> <p> <strong>The question:</strong></p> <p>Do i need the 1.1.0 version, and if so... where can i find it?</p> <p> </p> <p> <strong>Case 2:</strong></p> <p> </p> <p>All the npm dependencies are registered on the <em> <strong>js_loader_modules</strong>, this file its quite big, </em></p> <p> <a href="https://issues.liferay.com/browse/LPS-82808?attachmentViewMode=list">i saw a resolve issue about it</a>, and install the FP6</p> <p>an the results (attached npmDeduplicationMinifiedOutTheBox.PNG &amp; npmDeduplicationSample.PNG):</p> <p> </p> <p>A consumer portlet with a minified version of js_loader_module with register dependencies (Angular) on it from provider module.</p> <p>Browser transfer info of js_loader_module: 2mb@1.55s  </p> <p> </p> <p> <strong>The question:</strong></p> <p> </p> <p>How to control the size of <em> <strong>js_loader_modules </strong>when we register common dependencies and it gets even bigger?</em></p> <p> </p> <p>Im using:</p> <p>DXP 7.1 with FP6</p> <p>Tomcat bundle with hsql</p> <p> </p> <p>Many thanks</p> <p> </p> <p>Regards.</p>

Armando Del Rosario 2019-01-14T18:30:38Z