-
Notifications
You must be signed in to change notification settings - Fork 84
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
"Unable to load compilation data: No root directory found" #177
Comments
Does this happen on the reason-react example repo, for example? Or could you point me to a repo where this behavior shows up? |
I just had the same error. In my case the problem was having a folder name with spaces: Renaming the folder fixed the issue: |
i have the same issue too, on ubuntu 18.04, vscode 1.29.1, renaming does no help, and it happens on any repo, including the reason-react example repo. |
With log:
|
If the path to project contains spaces, it will get same error. |
@hackwaly I think there's no spaces in the path of the project as the log shows
|
High light the related error log:
|
Hello, does not work:
works:
Would that be possible to support '@' ?, never had this problem before with VSCode |
I'm getting the same issue. Using Visual Studio Code version 1.35.1. I make a new folder and just have an empty As far as I can tell, there are no spaces in any paths, as some previous comments have suggested might be the source of the problem. Here's the
|
Hmm...
|
debug errors:
|
If I open Jane Street's Core, I didn't get this error. but it says can't find the
|
@jaredly This error occurs if |
If you add only the configuration file, you will get a |
@imbsky I still run into this issue regardless of it seems like this has to do with conflicting versions somewhere on my machine. pretty sure this only began to occur after i upgraded to the last version about a week ago. |
I don't use this extension anymore. |
Same problem here....Unable to load compilation data: No root directory found! |
See my comment here for workarounds. |
From @joelonsql on November 8, 2018 7:44
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes/No
Copied from original issue: microsoft/vscode#62766
The text was updated successfully, but these errors were encountered: