This fixes a bug where, when packaging an extension, the extension developer would receive the error Unexpected token (1:0)
The problem is that if the extension had an icon, the icon file would be included in the list of files to search for require statements. Because the icon file is not JavaScript, the strip-comments process would fail when parsing the file.
Description
This fixes a bug where, when packaging an extension, the extension developer would receive the error
Unexpected token (1:0)
The problem is that if the extension had an icon, the icon file would be included in the list of files to search for require statements. Because the icon file is not JavaScript, the
strip-comments
process would fail when parsing the file.Related Issue
https://jira.corp.adobe.com/browse/DTM-15226
Motivation and Context
Let extension developers package extensions successfully.
How Has This Been Tested?
I ran the updated packager on a few Adobe extensions.
Screenshots (if appropriate):
Types of changes
Checklist: