Optimize size and transfer time of AMD Loader configuration

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X, Master
• Fix Version/s: 7.0.0 DXP FP55, 7.0.0 DXP SP9, 7.0.X, 7.1.10 DXP FP1, 7.1.1 CE GA2, 7.1.10.1 SP1, 7.1.X, Master
• Component/s: AMD Module Loader, ~ [Archived] Frontend Infrastructure
• Labels:
  • backend_test
  • ee-ts
  • liferay-dxp-70-sp9
  • liferay-dxp-71-sp1
  • liferay-fixpack-de-55-7010
  • liferay-fixpack-dxp-1-7110
• Branch Version/s:
  7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Story Points: 0.25
• Fix Priority: 4
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/61108

Currently the /o/js_loader_modules endpoint is returning a document of 1.5MB which is way too big to be retrieved for each page refresh. It could even be bigger as more npm modules are deployed.

We need to cut both in size (minify it) and transfer time (gzip it for transfer).

---

Steps to reproduce (I)

1. Start portal
2. Open Chrome dev tools, network tab
3. Request http://localhost:8080/o/js_loader_modules from the browser

Expected results:

1. A document of around 817KB should be produced

Actual results:

1. A document of around 1.5MB is produced

---

Steps to reproduce (II)

1. Stop portal
2. Edit portal.properties, set gzip.compression.level property to 1 (by default it is -1)
3. Start portal
4. Open Chrome dev tools, network tab
5. Request http://localhost:8080/o/js_loader_modules from the browser

Expected results:

1. A document of around 817KB should be produced but only ~136KB should be transferred (see image below)

Actual results:

1. A document of around 1.5MB is produced and transferred