-
Notifications
You must be signed in to change notification settings - Fork 60
bs binaries paths are determined wrong in monorepos #10
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
Comments
Second this, it doesn't work in monorepos 😞 A solution in the short term could be to have a "bsb path"/"bsc path" settings maybe? It's something that could be useful anyway 😄 |
We as well use yarn workspaces and have lost formatting. |
Came here to open the same issue. |
@BlueHotDog you can already get the extension working with monorepos if you use this branch: #16 it works fine so far 😄 |
I worked around this for the time being by adding this
and then running:
Alternatively you can do this globally by modifying the
to this:
|
We rather wait until this extension stabilizes. this issue is open for 4 months, with open Prs trying to fix this. can any maintain please help here? |
Hey guys, check this out if you are using yarn workspaces, I have a PR in that has a current release flag that you can try for vim plug. |
rescript-vscode/server/src/server.ts
Line 291 in ba96a2f
E.g. this wouldn't work for monorepos that use yarn workspaces, b/c binaries are hoisted above the bsconfig's node_modules.
The text was updated successfully, but these errors were encountered: