Nikolay Borzov

I think `npm run affected:lint --fix --file` is a bad candidate for linting on commit because it could unwrap a list of changed files into all files in the project.

From the README > Mapped code without source. It might be code generated by a bundler (e.g. webpack). Represented by [no source] in explore result. It means there are record...

Maybe after 2.0 release. But we need more details about how a list of changes should look like.

Please provide the exact CLI command. What is result looks like in JSON format? This is blank CRA 

> Is the weird recursive nesting artifact normal, or abnormal for a mature project? A visualization like this looks abnormal to me. Could post the result of `yarn source-map-explorer 'build/static/js/*.js'...

I expect more details. Provide the list of files inside `build/static/js/`

I see a problem with `.LICENSE.txt` file. For now, you need to use a glob that only matches ` .js` and `.js.map` files. The issue is noted

Have you tried omitting single quotes? ``` source-map-explorer build/static/js/*.js ```

What terminal do you use? Try Git Bash

Please read https://github.com/danvk/source-map-explorer/blob/master/CONTRIBUTING.md. webtreemap will be replaced with foamtree in 2.5.0