Currently, when opening a 7.2 DXP production-ready bundle, there will be this warning in the Chrome DevTools console:
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:
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.