Closed mklingn closed 5 years ago
I have the same issue.
You can also change package.json and stay in 1.1.4 :
- "coc.nvim": "^0.0.73",
+ "coc.nvim": "0.0.71",
- "vscode-languageserver-protocol": "^3.15.0-next.6",
+ "vscode-languageserver-protocol": "3.15.0-next.6",
- "vue-language-server": "^0.0.60"
+ "vue-language-server": "0.0.57"
For anybody wondering, the diffs from @ladevieq are meant to be applied to ~/.local/share/nvim/plugged/coc.nvim/package.json.
One could probably also fix coc-vetur to 1.1.3 in ~/.config/coc/extensions/package.json.
But most likely one will forget having done so and experience strange effects in the not so far future...
First off: Thanks for the great tool.
I found an issue with release version 1.1.4. Below is the output of
:CocInfo
.versions
vim version: NVIM v0.3.4
node version: v12.7.0
coc.nvim version: 0.0.74-c97d41aa1e
term: screen
platform: linux
Messages
[coc.nvim] Request initialize failed with message: The "path" argument must be of type string. Received type undefined
[coc.nvim] Server Vetur Language Server failed to start: Request initialize failed with message: The "path" argument must be of type string. Received type undefined
Downgrading to release version 1.1.3 fixes the issue.