Description
This issue is automatically created based on existing pull request: #33850: Reduce async console logger
Description (*)
Draft test
path
https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Ui/view/base/web/js/lib/logger/console-logger.js
Out of curiousity do we actually need log always load at all page? Should have config allow we on/off load this or exclude it in production ?
Before this changes
Home 187/219 js requests
Category 190/223 js requests
Details 209/250 js requests
Checkout 317/389 js requests
After this changes
Home 178/215 js requests
Category 181/225 js requests
Details 200/247 js requests
Checkout 308/379 js requests
we no longer load around ~10 files. The best scenario not errors we have no longer load additional 10 files. But the worse case. When we got something goes wrong, we need log to indicate what problem and where it happen
Functionals works without affected
No new update since 2017
cc: @VladimirZaets Can you give me some explain or related docs for this. Thanks you
Related Pull Requests
Fixed Issues (if relevant)
- Fixes magento/magento2#<issue_number>
Manual testing scenarios (*)
- ...
- ...
Questions or comments
Contribution checklist (*)
- Pull request has a meaningful description of its purpose
- All commits are accompanied by meaningful commit messages
- All new or changed code is covered with unit/integration tests (if applicable)
- README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
- All automated tests passed successfully (all builds are green)