The stylelint server crashed 5 times in the last 3 minutes. The server will not be restarted.
See original GitHub issuedescription
When install stylelint globally, and set stylelint.stylelintPath to the global path, stylelint server crashes when vscode starts.
info
This is the vscode version info.
Version: 1.44.0
Commit: 2aae1f26c72891c399f860409176fe435a154b13
Date: 2020-04-08T08:23:56.137Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.4.0
What vscode-stylelint configuration is needed to reproduce the bug?
"stylelint.enable": true,
"stylelint.stylelintPath": "/Users/username/.nvm/versions/node/v14.0.0/bin/stylelint",
"editor.codeActionsOnSave": { "source.fixAll": true },
Is this issue related to autofix? (
editor.codeActionsOnSave)
No.
Which version of vscode-stylelint are you using?
0.84.0
Which version of stylelint are you using?
13.3.3
Does your issue relate to non-standard syntax (e.g. SCSS, nesting, etc.)?
no
What did you expect to happen?
globally installed stylelint should work since configuration item stylelint.stylelintPath has been provided.
What actually happened (e.g. what warnings or errors you are getting)?
vscode 'official' extension crashed
This issue has nothing to do with style lint
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Related StackOverflow Question
It’s probably a problem with the library
global-modulesused bystylelint. It seems that usingnvmmay not return the correct global module path.https://github.com/jonschlinkert/global-modules/issues/7
It may work if you specify the full path in config.
Hi @multics. I think that if you specify the Node module in “stylelint.stylelintPath”, it will work. e.g.
"stylelint.stylelintPath": "/usr/local/lib/node_modules/stylelint"Even if “bin” is specified, it does not work.