Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create separate analyzer.report.html for cht-form component #9878

Open
jkuester opened this issue Apr 3, 2025 · 0 comments
Open

Create separate analyzer.report.html for cht-form component #9878

jkuester opened this issue Apr 3, 2025 · 0 comments
Assignees
Labels
Type: Technical issue Improve something that users won't notice

Comments

@jkuester
Copy link
Contributor

jkuester commented Apr 3, 2025

Describe the issue
Twice now I have wasted a ton of time while investigating webapp bundle sizes because I did not realize that the webapp/analyzer.report.html file that gets created when running npm run build will be populated with data about the cht-form build since that runs after the actual webapp build. Basically the webapp/analyzer.report.html file from the webapp build gets overwritten by the cht-form one.

(Yes a wiser person would have logged this issue after the first time this happened... :🤦)

Describe the improvement you'd like
I think it should be fine if we can just write a separate report file for cht-form.

Describe alternatives you've considered

Alternatively, we could just not write a report for cht-form since we are not so sensitive about its bundle size...

@jkuester jkuester added the Type: Technical issue Improve something that users won't notice label Apr 3, 2025
@jkuester jkuester self-assigned this Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Technical issue Improve something that users won't notice
Projects
None yet
Development

No branches or pull requests

1 participant