Describe the bug
Today, I updated my vim & vim plugins and coc stopped working. At first I had no idea why that was, then I opened :messages and saw this pop up:
[coc.nvim] Error loading extension from /Users/tomaskallup/.config/coc/extensions/node_modules/coc-eslint/lib/index.js: process.binding(...).internalModuleReadFile is not a function
[coc.nvim] Error loading extension from /Users/tomaskallup/.config/coc/extensions/node_modules/coc-html/lib/index.js: process.binding(...).internalModuleReadFile is not a function
[coc.nvim] Error loading extension from /Users/tomaskallup/.config/coc/extensions/node_modules/coc-json/lib/index.js: process.binding(...).internalModuleReadFile is not a function
[coc.nvim] Error loading extension from /Users/tomaskallup/.config/coc/extensions/node_modules/coc-tslint/lib/index.js: process.binding(...).internalModuleReadFile is not a function
[coc.nvim] Error loading extension from /Users/tomaskallup/.config/coc/extensions/node_modules/coc-css/lib/index.js: process.binding(...).internalModuleReadFile is not a function
[coc.nvim] Error loading extension from /Users/tomaskallup/.config/coc/extensions/node_modules/coc-tsserver/lib/index.js: process.binding(...).internalModuleReadFile is not a function
I tried running :CocUpdate, but that didn't help either. At first I though it could be node related, but my node version is still 8.12.0.
Any idea what this could be related to or where I should look?
Desktop (please complete the following information):
I noticed the same. This is happening after https://github.com/neoclide/coc.nvim/commit/31b70afae974a0ca656207e9304ae446ad7371ef to use Node 10. Will be necessary some changes on the extensions.
Found that internalModuleReadFile was renamed to internalModuleReadJSON :cry:
In node 10 it was renamed, but I'm still on node 8.12, so there's something wierd going on 馃
It's a problem with pkg project I think https://github.com/zeit/pkg/issues/467 and https://github.com/zeit/pkg/pull/461
Yea, seems like it. My current workaround is just git reset HEAD~1 && yarn install in coc.nvim folder.
I've rebuild the binary with node 8 and upload the binary again, it should be fixed after run :call coc#util#install().
Sorry for the unconvience, I changed to use node 10 because I'm not able to download node binary required by pkg yesterday and didn't notice node 10 with pkg not working.
@tomaskallup if you wish to have a less unstable plugin list, for the ones that have releases like coc, with vim-plug you can add plugins like Plug 'fatih/vim-go', { 'tag': '*' }, so it only upgrades on new tags. I do that for vim-go b/c the author itself recommended not to use master and do that instead.
Most helpful comment
@tomaskallup if you wish to have a less unstable plugin list, for the ones that have releases like coc, with vim-plug you can add plugins like
Plug 'fatih/vim-go', { 'tag': '*' }, so it only upgrades on new tags. I do that for vim-go b/c the author itself recommended not to use master and do that instead.