eventregistration.js triggers build warning regarding size limit
See original GitHub issueWhere to find the issue
https://github.com/corona-warn-app/cwa-website/blob/master/src/assets/js/eventregistration.js
Describe the issue
When the website is built through https://github.com/corona-warn-app/cwa-website/blob/master/.github/workflows/build.yml a warning is shown regarding eventregistration.js
.
WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
eventregistration.js (658 KiB)
For example the pull request https://github.com/corona-warn-app/cwa-website/pull/1167 triggered the action which is shown in the logs under https://github.com/corona-warn-app/cwa-website/actions/runs/788829128. Here is the relevant part of the log:
Built at: 04/27/2021 11:00:24 AM
Asset Size Chunks Chunk Names
app.js 139 KiB 0 [emitted] app
eventregistration.js 658 KiB 1 [emitted] [big] eventregistration
Entrypoint app = app.js
Entrypoint eventregistration [big] = eventregistration.js
WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
eventregistration.js (658 KiB)
WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
eventregistration (658 KiB)
eventregistration.js
WARNING in webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/
Suggested change
Please consider if something should be done to avoid this warning appearing.
Internal Tracking ID: EXPOSUREAPP-13404
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Webpack - WARNING in asset size limit: The following asset(s ...
Webpacks warning size seems out of date. Instead of just ignoring it you can set it to a more meaningful size limit. module.exports...
Read more >Known issues and workarounds (Dynamics 365 Marketing)
This document provides important, late-breaking information about known issues and workarounds for Dynamics 365 Marketing.
Read more >Controlling maximum request size
Accessing these variables or functions with a request payload that exceeds the maximum size causes the service to respond with error code 400....
Read more >emscripten.h — Emscripten 3.1.26-git (dev) documentation
This allows you to declare JavaScript in your C code “inline”, which is then executed when your compiled code is run in the...
Read more >Webpack performance budgets and asset size limit warning ...
Per #3216 @addyosmani said "Highlight at build-time any JavaScript chunks or bundles" so should it apply or not apply to images? If this...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@MikeMcC399 Thank you for reporting the issue and all the information. Internal Tracking ID: EXPOSUREAPP-13404
@Ein-Tim
This is a question for a JavaScript expert.
“bug” is the correct label until an expert qualifies the issue and says it can be dismissed or the issue has been addressed. The Open Source Team has so far not responded.
In the meantime the
npm run build
reports thateventregistration.js
has grown even further in sizeand that there is a problem additionally with
cwaa.js