Semantic versioning of npm dependencies not correctly resolved

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.0.0 DXP FP37, 7.0.0 DXP SP7, 7.0.5 CE GA6, 7.0.X, 7.1.0 M1, 7.1.X, Master
• Component/s: AMD Module Loader
• Labels:
  • liferay-digital-enterprise-70-sp7
  • liferay-fixpack-de-37-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/53250

Steps to test:

1. Start the portal
2. Deploy the two attached portlets
3. Request http://localhost:8080/o/js_loader_modules in the browser
4. Look for "lris-jquery-testcase-web@1.0.0/js/index.es" (it appears more than once) and assert that one of its appearances matches the picture below:
5. Look for "lris-jquery-current-web@1.0.0/js/index.es" (it appears more than once) and assert that one of its appearances matches the picture below:

In both cases, jquery@3.2.1 and not jquery@3.2.0 should appear.

Currently, the "lris-jquery-current-web@1.0.0/js/index.es" case is showing jquery@3.2.0 (when the bug is reproduced).