Coc.nvim: javascript bundle not found

Created on 12 Sep 2020 · 20Comments · Source: neoclide/coc.nvim

Describe the bug

I cant open vim since the last update (0.0.79) (e5cedd3)

Screenshots (optional)

Screenshot_20200912_174347

Source

GGCristo

👍6

Most helpful comment

Running macOS Catalina and vim with Pathogen, I had just git cloned coc.nvim from master and was seeing the same problem. Read above that getting back to tag v0.0.78 would get it working for now, and this is all it took. Thanks.

cd ~/.vim/bundle/coc.nvim
git checkout tags/v0.0.78

FrankReh on 17 Oct 2020

👍3

All 20 comments

Running into the same issue just now. And the auto installation results a building failure in my neovim (triggered by that coc util install)

  $ npm-run-all clean build
  yarn run v1.22.5
  $ rimraf lib build
  Done in 0.22s.
  yarn run v1.22.5
  $ tsc -p tsconfig.json
  error TS5058: The specified path does not exist: 'tsconfig.json'.
  error Command failed with exit code 1.
  info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
  ERROR: "build" exited with 1.
  error Command failed with exit code 1.
  info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

jethrosun on 12 Sep 2020

👍3

yarn install v1.22.4
info No lockfile found.
[1/5] Validating package.json...
[2/5] Resolving packages...
warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom > [email protected]: request-promise-native has
been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom > [email protected]: request has been deprecated, see https://
github.com/request/request/issues/3142
warning jest > jest-cli > jest-config > jest-environment-jsdom > jsdom > request > [email protected]: this library is no longer
supported
warning jest > @jest/core > jest-haste-map > sane > micromatch > snapdragon > source-map-resolve > [email protected]: https://gith
ub.com/lydell/resolve-url#deprecated
warning jest > @jest/core > jest-haste-map > sane > micromatch > snapdragon > source-map-resolve > [email protected]: Please see https://
github.com/lydell/urix#deprecated
[3/5] Fetching packages...
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning " > @typescript-eslint/[email protected]" has unmet peer dependency "tslint@^5.0.0 || ^6.0.0".
[5/5] Building fresh packages...
$ npm-run-all clean build
yarn run v1.22.4
$ rimraf lib build
Done in 0.13s.
yarn run v1.22.4
$ tsc -p tsconfig.json
error TS5058: The specified path does not exist: 'tsconfig.json'.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "build" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

[Process exited 1]

Congee on 12 Sep 2020

👍1

mabe this comment can help, even if it's not the same problem.

mirsella on 12 Sep 2020

Looks like vim-plug tend to use latest tag instead of default branch when the tag is newer.
Should be fixed now.

chemzqm on 12 Sep 2020

👍1

Bad release script added bin/server.js, fixed now.

chemzqm on 12 Sep 2020

Getting [coc.nvim] build/index.js not found, reinstall coc.nvim to fix it. now, CocRebuild doesn't seem to help.

katsika on 12 Sep 2020

You may need run git reset head --hard in folder of coc.nvim and update it by :PlugUpdate in your vim.

chemzqm on 12 Sep 2020

👍3

@chemzqm Perfect, thanks! Works now.

katsika on 12 Sep 2020

@chemzqm getting the same "javascript bundle not found" error on master. Reverting to release branch (tag v0.0.79) works.
Latest bad commit on master: 9918875

AdrienLemaire on 2 Oct 2020

You have to build javascript when using master

chemzqm on 2 Oct 2020

👍1

Seem that v0.0.79 is still broken. If I manually go in and switch to version v0.0.78 and remove the node_modules directory then things install fine and are working. As soon as I run a PlugUpdate then version v0.0.79 is installed and my Neovim is broken with yarn trying to run and install the missing tsconfig.json again. When is this going to get fixed?

timnolte on 4 Oct 2020

v0.0.79 is broken, use latest release branch or wait for next release tag.

chemzqm on 4 Oct 2020

OK, I found that I had specified {'tag': '*'} so every time I would run :PlugUpdate it would still update to the latest tagged release. Wouldn't it be wise to remove that release tag since it's bad? Anyways, I changed my config to use {'branch': 'release'} and things are working. Thanks!

timnolte on 4 Oct 2020

For anyone else who might find this I did as @timnolte did but I also did as @chemzqm suggested above and git reset head --hard then a :PlugUpdate to fix the issue.

travisboss on 6 Oct 2020

cd ~/.vim/bundle/coc.nvim/ && git reset head --hard
open vim && :PluginUpdate && :call coc#util#install()

Shokodemon on 15 Oct 2020

cd ~/.vim/bundle/coc.nvim/ && git reset head --hard
open vim && :PluginUpdate && :call coc#util#install()

^^This!! Running macos catalina with neo plug (was running vundle before, but was having issues).
Was looking for hours for this solution.

magidandrew on 16 Oct 2020

🚀1 🎉1 👍1

cd ~/.vim/bundle/coc.nvim
git checkout tags/v0.0.78

FrankReh on 17 Oct 2020

👍3

I also run into this problem on Debian with neovim and Vundle as plugin manager. Tried resetting, wiping, reinstalling, without success. Checking the same release as @FrankReh - v0.0.78 - did fix the problem for now.