Eslint-fix failed

version number

ESLint Version: 4.18.2
Node Version: 8.93
npm Version: 5.5.1

package.json part

scripts": {
    "dev": "webpack-dev-server --open --history-api-fallback",
    "build": "webpack -p",
    "test": "echo \"Error: no test specified\" && exit 1",
    "lint": "eslint **/*.js",
    "lint-html": "eslint **/*.js -f html -o ./reports/lint-results.html",
    "lint-fix": "eslint --fix **/*.js"
  }

error

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-blog@1.0.0 lint: `eslint **/*.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-blog@1.0.0 lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\yanyue\AppData\Roaming\npm-cache\_logs\2018-04-03T09_10_39_948Z-debug.log

debug.log

0 info it worked if it ends with ok
1 verbose cli [ "D:\\Alike\\Environment\\nodejs\\node.exe",
1 verbose cli   "D:\\Alike\\Environment\\nodejs\\node_modules\\npm\\bin\\npm-cli.js",
1 verbose cli   "run",
1 verbose cli   "lint",
1 verbose cli   "--fix" ]
2 info using npm@5.5.1
3 info using node@v8.9.3
4 verbose run-script [ "prelint", "lint", "postlint" ]
5 info lifecycle react-blog@1.0.0~prelint: react-blog@1.0.0
6 info lifecycle react-blog@1.0.0~lint: react-blog@1.0.0
7 verbose lifecycle react-blog@1.0.0~lint: unsafe-perm in lifecycle true
8 verbose lifecycle react-blog@1.0.0~lint: PATH: D:\Alike\Environment\nodejs\node_modules\npm\bin\node-gyp-bin;e:\Front-end\react-blog\node_modules\.bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;D:\Alike\TortoiseGit\bin;D:\Alike\Environment\java-jdk-1.70\bin;D:\Alike\Environment\nodejs\;C:\Program Files\TortoiseSVN\bin;D:\Alike\A-PCMaster\Git LFS\Git LFS;D:\Alike\pandoc\;C:\Users\yanyue\AppData\Roaming\npm;C:\Program Files (x86)\Microsoft VS Code\bin
9 verbose lifecycle react-blog@1.0.0~lint: CWD: e:\Front-end\react-blog
10 silly lifecycle react-blog@1.0.0~lint: Args: [ "/d /s /c", "eslint **/*.js" ]
11 silly lifecycle react-blog@1.0.0~lint: Returned: code: 1  signal: null
12 info lifecycle react-blog@1.0.0~lint: Failed to exec lint script
13 verbose stack Error: react-blog@1.0.0 lint: `eslint **/*.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (D:\Alike\Environment\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:280:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (D:\Alike\Environment\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid react-blog@1.0.0
15 verbose cwd e:\Front-end\react-blog
16 verbose Windows_NT 6.1.7601
17 verbose argv "D:\\Alike\\Environment\\nodejs\\node.exe" "D:\\Alike\\Environment\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "lint" "--fix"
18 verbose node v8.9.3
19 verbose npm  v5.5.1
20 error code ELIFECYCLE
21 error errno 1
22 error react-blog@1.0.0 lint: `eslint **/*.js`
22 error Exit status 1
23 error Failed at the react-blog@1.0.0 lint script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Let"s take a look at how I can solve this problem. I can"t fix the code by using eslint.

Mar.02,2021

post a complete error message. I don't think is reporting an error .

eslint can't fix all the code, just look at the eslint documentation and you can see that -- fix can only fix those fixable rules.

when eslint detects an error or warning, it returns a code that is not 0, and npm err!

appears.

so don't make a fuss when you see npm ERR. It's not an error in running the program, but something wrong with your code.

this is not reporting an error.

Menu