LSP: LSP-eslint exits unexpectedly in ST 4098 due to non-conforming stdout input
in .TSX file , Here is the startup console:
LSP-eslint.sublime-settings:
{ "enabled": true, "settings": { "validate": [ "javascript", "javascriptreact", "vue", "typescript", "typescriptreact" ], "options": { "parserOptions": { "project": [ "./tsconfig.json" ], } }, } }
Need some help, Thx !
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 1
- Comments: 17 (13 by maintainers)
Commits related to this issue
- Add --node-ipc support Fix https://github.com/sublimelsp/LSP/issues/1612 — committed to alecmev/LSP by alecmev 2 years ago
- Add --node-ipc support Fix https://github.com/sublimelsp/LSP/issues/1612 — committed to alecmev/LSP by alecmev 2 years ago
- Add --node-ipc support Fix https://github.com/sublimelsp/LSP/issues/1612 — committed to alecmev/LSP by alecmev 2 years ago
It works! https://github.com/sublimelsp/LSP/pull/2015
Wish I would remember that I’ve investigated it before. 😃
Moved this to the LSP repo.
At the minimum, we should print the exception to make cases like this easier to diagnose in the future.
Possibly we can gracefully handle such cases and just print those non-recognized messages to the LSP log panel.
here is a test demo: https://github.com/tamamadesu/eslint-test