We need rollup brfs to inline the fs stuff (existing brfs plugin doesnt work for esm).

You could do what build-viewer does to work around this for now.

We need rollup brfs to inline the fs stuff (existing brfs plugin doesnt work for esm).

We already include the localized strings in the flow report. If we inline the file we'll just be adding the again. _formatMessage doesn't access the localized strings on it's own so this method works, or we could shim 'fs'.

Oh, I meant just inlining the list of "CANONICAL_LOCALES", which flow report doesn't necessarily need anyhow, so you could also just not (there is an explicit check at runtime for whether fs exists).

If you shim locales.js to an empty object (see https://github.com/GoogleChrome/lighthouse/blob/master/build/build-viewer.js#L67) and replace __dirname, you should be able to avoid restructuring shared/localization.

cc @brendankenny on whether or not splitting up format.js makes sense.

Bundled output look ok?

Ya locales are included, but only once.