JS analysis blockers ☂️

[connorjclark]

Some stuff is now landing in the experimental config. The plan is to move everything to default once these items have been resolved.

• workaround CORS for fetching maps
• the audits
• • legacy-javascript
• • • initial implementation
• • • use source maps
• • • third party web
• • • opportunity
• • • tweak web dev guide
• • unused-javascript source map augmentation
• • duplicated-javascript
• • valid-sourcemaps
• fix subRows alignment style issues
• treemap visualization
• visibility in the report
• web.dev article ("here's what source maps can let us do", focus of the 6.x whats new article)
• docs. mention how other big sites export source maps. how to lock it down to select users (if that is a concern - also explain that then, PSI etc. wouldn't work)

[connorjclark]

@paulirish IIRC you made a mock of how to link to the treemap visualization in the report. something like a big rectangle next to where "View Trace" would be. where'd that go?