Kael

merge for now

@jmc-88 `cmd -c start` is the very better way

/close for now Be free to reopen the issue if necessary

actually it is quite easy to work it out with `assign` ```js const sorted = assign({}, parsed, Object.keys(parsed).sort()) ```

I can't understand your question. could you provide minimum slices of code and the expected result?

Is it for performance purposes? But why do we write such a silly ignore rule set as `['**/coverage', '!**/coverage']`?

Could you provide the use cases or concrete code slices? Is it only a linting warning about potential issues or are there any real failures? Here is the test case...

It is really weird that `tsc` treats packages with/without `type: module` differently. - ❌ `tsc ./src/lib/is-ignored/index.ts --moduleResolution Node16` failed with `type:module` in package.json - ✅ `tsc ./src/lib/is-ignored/index.ts --moduleResolution Node16` succeeded...

Frankly speaking, you got a good point. The case 6 encounters the situation that the path is **indirectly** unignored. However, changing the behavior of the `TestResult` object will bring a...

Since your use case involves file structure traversing, and if a directory is ignored, everything inside it is definitely ignored. And in fact, the child directory could not unignore its...