This is probably not a problem with npm. There is likely additional logging output above.
See original GitHub issueTell us about your environment
- ESLint Version: 4.18.2
- Node Version: 8.93
- npm Version: 5.5.1
What parser (default, Babel-ESLint, etc.) are you using?
Please show your full configuration:
Configuration
{
"name": "react-blog",
"version": "1.0.0",
"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"
},
"dependencies": {
"antd": "^3.3.1",
"babel-plugin-import": "^1.6.7",
"jquery": "^3.3.1",
"puppeteer": "^1.2.0",
"react": "^16.2.0",
"react-dom": "^16.2.0",
"react-router-dom": "^4.2.2"
},
"devDependencies": {
"babel-cli": "^6.26.0",
"babel-core": "^6.26.0",
"babel-loader": "^7.1.2",
"babel-preset-es2015": "^6.24.1",
"babel-preset-react": "^6.24.1",
"bundle-loader": "^0.5.5",
"cross-env": "^5.1.3",
"css-loader": "^0.28.9",
"eslint": "^4.18.2",
"eslint-config-airbnb-base": "^12.1.0",
"eslint-loader": "^2.0.0",
"eslint-plugin-import": "^2.9.0",
"file-loader": "^1.1.6",
"history": "^4.7.2",
"html-webpack-plugin": "^2.30.1",
"jsx-loader": "^0.13.2",
"open-browser-webpack-plugin": "0.0.5",
"react-router": "^4.2.0",
"style-loader": "^0.19.1",
"uglifyjs-webpack-plugin": "^1.1.6",
"url-loader": "^0.6.2",
"webpack": "^3.10.0",
"webpack-dev-server": "^2.9.7"
},
"license": "MIT"
}
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
https://github.com/xiaoyueyue165/react-blog
npm run lint --fix
What did you expect to happen?
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
What actually happened? Please include the actual, raw output from ESLint.
I don’t know how to do this. I haven’t been able to correct my mistake for a long time. I’m getting an error. Why is this? May you ask me questions.
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 ]
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
error: This is probably not a problem with npm. There is likely ...
As the error says itself this is not a problem with npm. Only we have to do is ... There is likely additional...
Read more >This is probably not a problem with npm. There is ... - GitHub
OS: windows 10 I'm using node version ( v10.15.3) and npm version (6.4.1) and I tried to create a simple react-app by using...
Read more >error This is probably not a problem with npm There is likely ...
This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run...
Read more >How to fix npm error This is probably not a problem with npm
This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run...
Read more >解决This is probably not a problem with npm. There is likely ...
This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This problem arises from the npm package which is incompatible with the react package you have. Try Updating both package or uninstall the package which is causing this problem.
Locking this issue since discussions about fixes for this error message are likely to be misleading to users that come across this issue in the future (see the above comment).