-
-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The stylelint server crashed 5 times in the last 3 minutes. The server will not be restarted. #104
Comments
output panel of
|
Hi @multics. |
Hi @ota-meshi, npm install -g stylelint stylelint-config-rational-order Here is the config: module.exports = {
extends: ['stylelint-config-rational-order'],
} BTW: command line execution has no problem. stylelint index.css div {
font-size: large;
color: black;
display: block;
} Do you have any suggestions? Thanks very much and have a nice day! |
It's probably a problem with the library jonschlinkert/global-modules#7 It may work if you specify the full path in config. module.exports = {
extends: [
'/path/to/.../node_modules/stylelint-config-rational-order',
// or
require.resolve('stylelint-config-rational-order'),
],
} |
Thanks @ota-meshi Yes, you are right. I am using Your help is appreciated! By the way, if this extension could be enhanced to support nvm users, the global config file would look nicer and node upgrades won't require the global config updated. That will be perfect! 😀 One more thing: |
When install
stylelint
globally, and setstylelint.stylelintPath
to the global path, stylelint server crashes when vscode starts.This is the vscode version info.
No.
0.84.0
13.3.3
no
globally installed stylelint should work since configuration item stylelint.stylelintPath has been provided.
vscode 'official' extension crashed
This issue has nothing to do with style lint
The text was updated successfully, but these errors were encountered: