John Yani

Do you have any `ts` files in the folder you're trying to lint? ``` find . -name '*.ts?' ```

Here's the config that triggers the error: https://github.com/facebook/create-react-app/blob/f5c3bdb65480f93b2d4a4c2f3214fc50753de434/packages/eslint-config-react-app/index.js#L57-L69 Apparently, `*.ts` files are being compiled even if you specify `js` glob pattern: `eslint './src/**/*.{js,jsx}'`. Maybe it's a bug in the eslint...

The "lint whole folder" task you mentioned suggests you're using VSCode. So maybe create an issue in the https://github.com/microsoft/vscode-eslint repo

@Chernavskikh I was referring to OP. Which task did you run? What's the output of `find . -name '*.ts?'`

@Lelith what's the command you're running?

@Kicu The plugin determines whether you're using Typescript or not by searching for *.ts files. You think you're not using ts while in fact you are. You can either continue...

@Lelith so the command you're running is `eslint .`. The dot means "current working directory". Which means it would lint all the files, even those you don't consider to be...

I was able to use this: https://github.com/sjonnet19/mocha-cobertura-reporter But unfortunately, absolute filenames are not recognized by cobertura.

Turns out the issue was that 3000 port was already used by another app. So marlin-config should either add a warning about 3000 port being already in use or choose...

Ok, so the issue is not that marlin can't provide an error message when 3000 is in use. The issue is that 3000 being in use by some other app...