Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-118828

Resolve warning on Chrome console: "DevTools failed to load SourceMap: Could not load content for popper.min.js.map"

    Details

      Description

      Currently, when opening a 7.2 DXP production-ready bundle, there will be this warning in the Chrome DevTools console:

      DevTools failed to load SourceMap: Could not load content for http://localhost:8080/popper.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
      

      This flags the inability of debugging popper.js, however, on the other hand, debug mode in Liferay is triggered by adding, among others, the below two properties:

      javascript.fast.load=false
      minifier.enabled=false
      

      With these 2 lines (both defaulting to true in a production bundle), the warning will no longer be printed and debug for popper.js source map will be possible.

      Although the warning in a production bundle can't be handled as a bug, it would nice if future releases of Liferay will include a set of changes not to make the warning appear in the console. Ideally, it is not desirable to have any 404s in production js log, and especially not caused by disabled debuggers.

        Attachments

          Activity

            People

            Assignee:
            support-lep@liferay.com SE Support
            Reporter:
            alfonso.crisci Alfonso Crisci (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:

                Packages

                Version Package