Open joelgriffith opened 7 years ago
This seems like a great idea. My suggestion would be, that we expose the underlying Chrome API, so people could use this for now until we found a good API.
Chrome's API is fairly low-level (they return ranges of coverage with booleans indicating covered or note). It's not an entirely valuable API unless you do some of the calc'ing yourself. It's also not an easy thing to implement as you have to collect resources loaded, and match them when coverage
is called (since Chrome references resources by a unique ID, and not by URI).
Chrome exposes a mechanism in which to get coverage for scripts. This type of information is crucial to front-end devs as it exposes unused code-paths. Would love to see an API for this