Nikolay Borzov

> @nikolay-borzov it's definitely zippier w/o the fade in/out effect. Could you share a visualization of that same set of source maps using webtreemap for comparison? You can get it...

Duplicate of #14

Thank you for your contribution. I'm considering switching source-map-explorer visualization to foam-tree https://github.com/danvk/source-map-explorer/issues/185. Take a look. We might change what is displayed inside visualization blocks

Exporting `convertRangesToLinesRanges()` won't help. We need to allow passing coverage data as an alternative to a coverage file path. And yes, the typing is kind of wrong

Agree with @galusben. From server we receive objects like: `{ attributes: { 'product.displayName': 'A product' } }`

On Windows I had to escape `\` ``` "test:coverage": "jest --coverage --changedSince=master --coverageThreshold=\"{\\\"global\\\":{\\\"statements\\\":80,\\\"branches\\\":80}}\"", ``` which results ``` jest --coverage --changedSince=master --coverageThreshold="{\"global\":{\"statements\":80,\"branches\":80}}" ```

Related https://github.com/bndr/pipreqs/issues/214

I see. Probably we should mention it in `CONTRIBUTING.md`

Well, `"main"` points to non-existing file meaning `import { } from 'webtreemap'` doesn't work

Separate CSS file worked just fine for my case. I already inject webtreemap js into HTML template anyway. We just paste content of `webtreemap.js` into generated HTML file. For now,...