Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: spawn eslint ENOENT

See original GitHub issue

I’m trying to migrate the project from lint-staged to nano-staged. Installed. Replaced configuration:

  "nano-staged": {
    "*.{js,ts,vue}": "eslint --cache --fix"
  },

Run

$ npx nano-staged
Nano Staged v0.3.1
- Preparing pipeliner...
  » Done backing up original repo state.
- Running tasks...
  *.{js,ts,vue} eslint --cache --fix
- Restoring to its original state...
  » Done restoring up to its original state.
- Removing patch files...
  » Done removing up patch files.

eslint --cache --fix:
Error: spawn eslint ENOENT

This is repeated with any command

  "nano-staged": {
    "*.{js,ts,vue}": "npx eslint --cache --fix"
  },

$ npx nano-staged
Nano Staged v0.3.1
- Preparing pipeliner...
  » Done backing up original repo state.
- Running tasks...
  *.{js,ts,vue} npx eslint --cache --fix
- Restoring to its original state...
  » Done restoring up to its original state.
- Removing patch files...
  » Done removing up patch files.

npx eslint --cache --fix:
Error: spawn npx ENOENT

  "nano-staged": {
    "*.{js,ts,vue}": "npm run lint"
  },

$ npx nano-staged
Nano Staged v0.3.1
- Preparing pipeliner...
  » Done backing up original repo state.
- Running tasks...
  *.{js,ts,vue} npm run lint
- Restoring to its original state...
  » Done restoring up to its original state.
- Removing patch files...
  » Done removing up patch files.

npm run lint:
Error: spawn npm ENOENT