npm bundle processor gets fooled when a main entry of a package.json starts with ./

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.0.0 DXP FP51, 7.0.0 DXP SP9, 7.0.X, 7.1.X, Master
• Component/s: JS Toolkit, ~ [Archived] Frontend Infrastructure
• Labels:
  • 7.1-must
  • liferay-dxp-70-sp9
  • liferay-fixpack-de-51-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 4
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/60279

Trying to deploy an npm package whose "main" field of "package.json" points to a module starting with "./" makes the FlatNPMBundleProcessor think that there's no "main" entry and thus fails.

An example of such package is chartjs-color-string@0.5.0.

Steps to reproduce:

1. Start portal
2. Deploy attached JAR file
3. Open http://localhost:8080/o/js_loader_modules in a browser
4. Look for [chartjs-color-string@0.5.0": \{exactMatch: true] (without the surrounding [ and ])

Expected results:

• You should see the following result:

Actual results:

• You see this, which is incorrect:

 

Notice how the "value" field changes in both screenshots.