-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
Update to latest Yarn 2/pnpify support #166
Comments
Thanks, I've updated readme |
Without updating MODULE_FOLDERS, coc-tsserver work only when vim's CWD is same with |
I didn't get it working, maybe I did something wrong:
What did I wrong? |
You need create |
ok working now thx. for others driving by you need to rerun btw, why can coc.vim not grab those three props from the standard |
You have to use |
hey i just tried it again to put those three props in my |
there is one interesting thing though: If a yarn add some module to some workspace I need to restart nvim to make tsserver aware of it. otherwise it shows still an error ( It's no big deal but is this intended? Or is it related to you last post? |
You make use |
Thanks again. For others driving by and also as note to myself: The easiest way to get a TS monorepo ready without intefereing with other non-yarn-2 projects is and without putting anything into the global
If you change anything think of rerunning the In VSCode you need to unlock the extension with Ctrl-Shift-p, choose Select TypeScript Version, pick Use Workspace Version. |
What I described one post above is not working anymore, e.g. I get all the time:
... despite having an CCing @arcanis : berry's editor support is shaky at best and not plug'n'play, rather trial'n'error. No rant but this is driving me nuts for days. Before I open an issue in your repo and create a bigger discussion, I would be happy about your feedback. I guees I must do something wrong. |
@arcanis ok I know what it was: Berry's lack on ESM support => yarnpkg/berry#638 |
Thanks for these instructions, needing to have typescript installed at the root before running
Anyone know how to fix this? |
I figured out the issue was that I did not launch vim from the root of the project, which makes sense because |
You can make |
That's a fair point, though as this file is shared with my development team we would either have to all have the repo in a common location or I would have to impose a machine-specific override of some sort. Can that path support any variables such as $HOME? |
Will support placeholder like VSCode, you can use |
Thanks for this. Apparently we have to install TypeScript in the root package.json and then also run |
I was having a hard time with getting this to work. What fixed it for me was running |
You deserve an equestrian monument in the main square of your city. |
yarnpkg/berry#1446 and yarnpkg/berry#1481 introduced first-class support for vim/coc via
yarn dlx @yarnpkg/pnpify --sdk vim
.I can confirm this works (as of Yarn v2.0.0-rc.36); a project-local
.vim/coc-settings.json
is generated with the following contents:This appears to have worked out of the box, so there's nothing needed in particular for coc-tsserver, besides updating the readme and perhaps simplifying the
MODULE_FOLDERS
lookupcoc-tsserver/src/server/utils/versionProvider.ts
Line 87 in ef22359
The text was updated successfully, but these errors were encountered: