Skip to content

launchIDE fails with missing vscode exports #3111

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

Closed
esarbe opened this issue Sep 13, 2017 · 0 comments
Closed

launchIDE fails with missing vscode exports #3111

esarbe opened this issue Sep 13, 2017 · 0 comments

Comments

@esarbe
Copy link
Contributor

esarbe commented Sep 13, 2017

launchIDE fails with missing vscode exports

> launchIDE
[warn] Multiple main classes detected.  Run 'show discoveredMainClasses' to see the list

> [email protected] update-all /home/esabe/source/dotty/vscode-dotty
> npm install && node ./node_modules/vscode/bin/install && curl -L -o out/coursier https://github.com/coursier/coursier/raw/v1.0.0-RC3/coursier

Detected VS Code engine version: ^1.12.0
Found minimal version that qualifies engine range: 1.12.0
Fetching vscode.d.ts from: https://raw.githubusercontent.com/Microsoft/vscode/72672be0b7d3eef0784077b880615f91b7ec85aa/src/vs/vscode.d.ts
vscode.d.ts successfully installed!

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   137  100   137    0     0     90      0  0:00:01  0:00:01 --:--:--    90
100 11814  100 11814    0     0   7113      0  0:00:01  0:00:01 --:--:--  7113

4 import { TextDocumentChangeEvent, TextDocument, Disposable, OutputChannel, FileSystemWatcher as VFileSystemWatcher, DiagnosticCollection, ProviderResult, CancellationToken, Position as VPosition, Location as VLocation, Range as VRange, CompletionItem as VCompletionItem, CompletionList as VCompletionList, SignatureHelp as VSignatureHelp, Definition as VDefinition, DocumentHighlight as VDocumentHighlight, SymbolInformation as VSymbolInformation, CodeActionContext as VCodeActionContext, Command as VCommand, CodeLens as VCodeLens, FormattingOptions as VFormattingOptions, TextEdit as VTextEdit, WorkspaceEdit as VWorkspaceEdit, Hover as VHover, DocumentLink as VDocumentLink, TextDocumentWillSaveEvent, WorkspaceFolder as VWorkspaceFolder } from 'vscode';
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   ~~~~~~~~~~~~~~~

vscode-dotty/node_modules/vscode-languageclient/lib/client.d.ts(4,706): error TS2305: Module ''vscode'' has no exported member 'WorkspaceFolder'.


1 import { WorkspaceFoldersChangeEvent as VWorkspaceFoldersChangeEvent } from 'vscode';
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~

vscode-dotty/node_modules/vscode-languageclient/lib/workspaceFolders.proposed.d.ts(1,10): error TS2305: Module ''vscode'' has no exported member 'WorkspaceFoldersChangeEvent'.

[error] Running command "/home/esabe/source/dotty/vscode-dotty/node_modules/.bin/tsc --pretty --project /home/esabe/source/dotty/vscode-dotty" failed.
[error] (vscode-dotty/compile:compile) Running command "/home/esabe/source/dotty/vscode-dotty/node_modules/.bin/tsc --pretty --project /home/esabe/source/dotty/vscode-dotty" failed.
[error] Total time: 11 s, completed Sep 13, 2017 11:16:38 AM
> exit
[esabe@localhost-localdomain dotty]$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working tree clean
[esabe@localhost-localdomain dotty]$ git pull
Already up-to-date.
[esabe@localhost-localdomain dotty]$ 
esarbe added a commit to esarbe/dotty that referenced this issue Sep 13, 2017
smarter added a commit to dotty-staging/dotty that referenced this issue Sep 15, 2017
Using "^2.2.1" means "Any 2.x.y version >= 2.2.1", this isn't great for
reproducibility in general, and it also broke the build because
vscode-languageclient 3.4.* depend on a newer vscode engine. This commit
avoids this issue by using fixed version numbers instead.
smarter added a commit that referenced this issue Oct 17, 2017
Fix #3111: Fix dependencies of vscode-dotty
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant