Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Possibly use packtracker.io to keep initial build sizes in check?
See original GitHub issueHi!
I’ve created a tool to measure and report webpack bundle stats. It is similar to webpack-bundle-analyzer except it’s a hosted service that reports this information directly into GitHub pull requests as Checks. Telling you the net effect of your changes, whether they’re growing your asset profile or not.
I’ve recently launched support for apps using your tool, and thought the project might benefit from running these checks on it’s pull requests. Helping to make sure proposed changes aren’t adversely effecting the tool’s initial bundle size.
I’ve also prepared a sample page showing the data of a blank CRA app.
If I can be of any help getting this set up let me know!
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
To be clear, I’m not suggesting it be included in default configurations, only that it could be used to measure this project for unexpected asset growth in a fresh CRA app.