Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

DevTools failed to load SourceMap: Could not load content for popper.min.js.map on Chrome browser

Written By

Liferay Support

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.

Issue

  • While using a production instance of Liferay, the below warning will appear in the Chrome 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

Environment

  • Liferay DXP 7.1
  • Liferay DXP 7.2
  • Liferay DXP 7.3
  • Liferay DXP 7.4

Resolution

  • The warning does not flag any Liferay bugs and can be safely ignored
  • As a client-side workaround, customers can navigate to the "Settings" for Developer Tools, then uncheck Enable JavaScript Sourcemaps under the "Sources" settings:
    js_devtools.png
  • The popper.min.js.map file, per se, allows the debugging of popper.js.
  • 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, the warning will no longer be printed and debug for Popper.js source map will be possible.
  • When in a production environment these properties are usually set to true. This implies the ComboServlet.java is used to group and efficiently load more files at the same time (JS or CSS), and the source maps are not being found and mapped correctly with their sources (for example, popper.min.js.map).

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?