Argument list too long

Description

I have a big project where I use a tslint, and I needed to check 450 files before committing, but an error occurred. But if I copy this command directly, there will be no error.

~/admin-webapp/node_modules/.bin/tslint: Argument list too long npm ERR! code ELIFECYCLE npm ERR! errno 126

My lint-staged config:

{
  "linters": {
    "*.ts": ["npm run lint", "git add"]
  },
  "ignore": ["**/*.spec.ts"]
}

package.json

 "lint": "tslint -c tslint.json --project src/tsconfig.json",

Steps to reproduce

Add more 360 files run lint-staged through npm run lint

Debug Logs

expand to view

~/admin-webapp/node_modules/.bin/tslint: Argument list too long
npm ERR! code ELIFECYCLE
npm ERR! errno 126

Environment

• OS: macOS High Sierra
• Node.js: v8.9.1
• lint-staged: v7.3.0

[okonet]

Yeah, but I think that’s the behavior I’d like to enforce in this case. Linting hundreds of files is no different from linting the whole project, which should be done on CI. It’s about common sense and best practices. I don’t want lint-staged to be the single point of failure.

[okonet]

I think we should just print a more friendlier message and suggest to skip the run for such cases. The splitting part is rather complex and makes the code harder to maintain. I also believe the case is so rare it’s not worth doing. I hardly believe there is value in using lint-stages on hundreds of files. CI should cover that. What do you think @sudo-suhas?