lint-staged installs husky 5 but sets up husky 4 config

[Pezmc]

Right now, if you run the following on an empty project:

$ npm init
$ npm install --save-dev prettier # or eslint or stylelint
$ npx mrm lint-staged

npx: installed 240 in 7.785s
Running lint-staged...
Update package.json
Installing lint-staged and husky...

+ husky@5.0.9
+ lint-staged@10.5.4

Note that husky 5.0.9 was installed, but our package.json looks like:

# cat package.json
{
  "name": "test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "dependencies": {},
  "devDependencies": {
    "husky": "^5.0.9",
    "lint-staged": "^10.5.4",
    "prettier": "^2.2.1"
  },
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "*.{js,css,md}": "prettier --write"
  }
}

Husky 5 no longer uses that config style format (see https://typicode.github.io/husky/#/?id=migrate-from-v4-to-v5), instead you need to run the commands like:

npx husky add .husky/pre-commit "npm run lint-staged"

The short term fix would be to update the task to only install Husky <5, which may be the preferred default since there are license complications right now.

mrm/packages/mrm-task-lint-staged/index.js

Line 7 in f213462

husky: '>=4',

Longer term, mrm should perhaps ask if the user prefers 4/5 and use the appropriate config format.

[okonet]

Thanks for submitting it! I agree we could quickly pin the version to 4 or migrate to the new format. Can you create a PR please?