Distributor ID: Ubuntu
Description:    Ubuntu 16.04.6 LTS
Release:        16.04
source-map-explorer Version [2.1.2]
Additional context

I can still see the /tmp/sme-result-2020113-220-1f3lsmg.3b1gf.html generated. I can still also put --html params and it will generate the file alright. I'm just wondering how to get the proper/expected behaviour if I am using WSL.
Couldn't test with [email protected] because it's too slow.
I tried with [email protected]
$ source-map-explorer build/static/js/*.js
build/static/js/2.9d3308cf.chunk.js
  Unable to map 130/5098425 bytes (0.00%)
build/static/js/main.b235dfa8.chunk.js
  Unable to map 124/248844 bytes (0.05%)
build/static/js/runtime~main.a8a9905a.js
  1. Your source map only contains one source (../webpack/bootstrap).
  This can happen if you use browserify+uglifyjs, for example, and don't set the --in-source-map flag to uglify.
  See https://github.com/danvk/source-map-explorer/blob/master/README.md#generating-source-maps
  2. Unable to map 62/1501 bytes (4.13%)
Unable to open web browser. Invalid switch - "/tmp".
Either run with --html, --json, --tsv, --file, or view HTML for the visualization at:
/tmp/sme-result-2020113-146-119t6vf.v2pk.html
$ source-map-explorer build/static/js/*.js --html ./some-file-name.html and manually open the some-file-name.html
Or use MINGW64 terminal on Windows
If anyone can have a better solution, kindly leave a comment below.