Flow tool remove-comments throws with unused suppression in [libs]

[wbinnssmith]

Flow version: 0.121.0
Flow tool version: 675c89d

Expected behavior

Flow tool remove-comments is able to either remove or ignore unused suppressions in definitions in [libs]

Actual behavior

Flow tool remove-comments throws:

uncaught rejection
[Error: ENOENT: no such file or directory, open '/path/to/project/[LIB] flow-libs/lib.js'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/path/to/project/[LIB] flow-libs/lib.js'
}
Error: ENOENT: no such file or directory, open '/path/to/project/[LIB] flow-libs/lib.js'

It looks like the file's name when processing errors includes the string [LIB] followed by a space.

To reproduce:

.flowconfig:

[libs]
flow-libs/

flow-libs/lib.js:

// @flow

declare module 'lib' {
	// $FlowFixMe
	declare export default number;
}

and run flow/tool remove-comments --bin path/to/flow .

[wbinnssmith]

cc @nmote @gabelevi (from the git blame for surrounding code)

[nmote]

This seems a bit odd. It's not a good idea to suppress errors in lib files, but you're right, the remove-comments tool should at least not crash. Feel free to CC me on a PR if you'd like to address it.

[mroch]

I believe it only shows [LIB] in the path when --strip-root is on. might be as simple as figuring out where that's set and whether it needs to be.